We are trying to analyze where the users come from with branch's getLatestReferringParams in React Native, however in iOS the params for ['+clicked_branch_link'] is always undefined when the actual sessions comes from a branch link, this problem is only happening with iOS (it's working with Android), and we have also tested trying to open this link via Chrome in the iPhone and it worked. I'm not completely sure if it's related to something going on with Safari or with the OS versions. Any guideline would be very welcome. Thanks Here is a small snippet of the code we are trying to implement
const lastParams = await branch.getLatestReferringParams()
const comesFromBranchLink = lastParams['+clicked_branch_link'] # Giving us undefined when it comes from a branch link
const isAReferralLink = lastParams['~feature'] === 'referral'
Edit: We tested again and basically it doesn't recognize the branch link, only if it comes from Google Chrome.
Alex from Branch.io here: this sounds like a possible configuration issue with Universal Links.
I see you have also submitted a ticket to our Integrations team, which is the quickest way to get a solution. I will make sure we follow up here with an update when the issue has been resolved!
Related
So, my team has been working on our Flutter app, trying to get a few of the deep links we created to open a website. And everything worked out fine...until we tried it on iOS devices. For iOS devices, the deep link behaves correctly only when typed out in the address bar, but when it's tapped on, be it in a TODO list, or through SMS messages, it takes you immediately to the installed app.
These behaviors, however, only occur for all URLs of the same host, for example:
https://foo.page.link/some-suffix
https://foo.page.link/baz/some-other-suffix
etc. you get the idea
Apparently, it's something to do with how iOS handle URL prefixes. This answer provides the best explanation and solutions I have found so far. However, these feel more like workarounds than solutions that would allow us to config our links like we did with Android. I'm asking here because the answer itself is almost two years old and there might already be simpler solutions out there.
These are the behaviors we defined for iOS and Android
Seems a few people had the issues too, but didn't figure a solution yet. For example I am having exactly the same this one.
Also according to this a reliable way to test if the universal link set up properly or not is to test the link in the notes app, which works for me. (Also works if I send the message with the link to myself.) However I can't open the app directly in most chat apps (eg. slack, discord) nor safari. On the other hand they works with the preview page on.
Anyone had a fix / workaround? Or that's just how it is (saw this might be issues with app trying to open the link in there build in browser and prevent redirecting somehow ?)
Any help or suggestion will be highly appreciated. Thank you in advance.
I had the same issue, enabling both universal links and custom url schemes for my dynamic link solved the issue.
Dynamic Links -> Edit Link -> Define link behavior for iOS
This is the setup:
I'm using Branch SDK for creating deep links and sharing them. If the app is installed, the link should've open it. But the link is always redirecting to app store except for the first link. The first link opens the app perfectly but any new links always redirect to the app store even though the app is installed.
I followed all the steps from documentation, https://docs.branch.io/pages/apps/ios/
but still no luck. Can you please help me find the problem?
Jackie from Branch here:
Here's our iOS integration guide you're looking for. We have code samples both in Swift and Objective C: https://docs.branch.io/pages/apps/ios/
If you continue to experience issues after you have gone through the troubleshoot docs(https://docs.branch.io/pages/apps/ios/#troubleshoot-issues), could you please reach out to us at integrations#branch.io with the following details?
Your Branch app ID
Detailed steps to reproduce
Links where the issue can be seen
Thanks!
My app has some code for opening directly to Google Maps. We're attempting to open directly to Street View for a particular coordinate using a URL like so:
comgooglemaps-x-callback://?center=47.613371,-122.313167&mapmode=streetview&x-success=myurlscheme://noop&x-source=MyApp
I'm seeing an infinite spinner with the Street View never loading.
This URL scheme is documented and has worked for several years, until a recent update.
https://developers.google.com/maps/documentation/ios-sdk/urlscheme
Is this feature of the app busted or did the URL scheme change?
This has been fixed in the latest release of google maps iOS app. Please check it.
Reference : https://github.com/googlemaps/OpenInGoogleMaps-iOS/issues/6
This is a bug ( or documentation needs updating) as I was able to verify this working with the previous Google Maps iOS build of 4.14(the last update). Also verified with other iOS apps that use StreetView.
submitted issue but this has not been acknowledged as a bug yet.
https://code.google.com/p/gmaps-api-issues/issues/list?can=2&q=streetview&colspec=ID+Type+Status+Introduced+Fixed+Summary+Internal+Stars&cells=tiles
It looks like it's been accepted as a bug according to Google. I've heard that it will be fixed with next update, but that is not official.
http://code.google.com/p/gmaps-api-issues/issues/detail?id=9095&q=apitype%3AIosSDK%20type%3ADefect&sort=-stars&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Internal%20Stars
Google has a new app, I believe we are supposed to use this instead but I've not tried it yet!! I still have not seen updated documentation on website that confirms this.
https://itunes.apple.com/us/app/google-street-view/id904418768?mt=8
https://github.com/googlemaps/OpenInGoogleMaps-iOS/issues/6
I read a post here. And I'm encountering this issue too. When I use FB.ui({method:'share'}) to share the content, the popup is not correctly working. But when I switched to the "old-school" way, putting a link: http://www.facebook.com/sharer.php?u=... it works fine.
I am just wondering why as a very popular browser, Chrome doesn't support this? Is there any technical reason for this?