ios-branch-deep-linking-attribution: Links not being created correctly

It seems to be the same problem as the https://github.com/BranchMetrics/ios-branch-deep-linking/issues/834 (closed issue ¯\_(ツ)_/¯) here on Peixe Urbano app, and like @joaopedro1520 said there, it doesn’t seems to be related to internet since our app relies entirely on it and is running fine on related scenario.

fail-link

on a sequence of about 5 tests, only 1 generated the short link. And this is happening for about some weeks, and here’s how it is influencing our sharing performance with about 45% of failed experiences:

The link work on WhatsApp sharing, but it fails if our user try it on Facebook, as you can see int this print:

img_6f34db632883-1

best,

About this issue

Hello,

The issue still occurs on iOS13. Sometimes branch generates a long link, sometimes - a short one without any code changes.

The device has a good network connection
A short link that was generated before is not cached, or at least is not retrieved from the cache, as mentioned above. Randomly a short or long link is generated for the same parameters (app-share-link).
the above mentioned ‘disableTracking’ is not mentionable for this case, as it was not used for our project.

Setting a timeout for branch requests did not help: e.g. Branch.getInstance().setNetworkTimeout(10)

It looks like the issue was server-side because the links are now being generated correctly again, without us changing anything 😊

Have you tried Edwards example code, where he used your exact parameters to create a link? Did it work as expected, or were you able to reproduce the issue? I have not been able to reproduce this issue on our side, when operating on our office network and my personal home WiFi network.
If you would like to provide your Branch App ID - I can test specifically for your Branch account.
I would also suggest testing this functionality with our TestBed App (Swift or Obj C).
You may then setup Branch TestBed app with your Branch keys, to see if you can reproduce the issue. If you can’t - that means that there is an integration issue. If you can - that means that something outside the app is causing this.

Let me know what you find out! Please remember that the detail of your response and finding will help us find the issue at a faster rate.