Search specific term/phrase surrounded by double quotes. e.g. “deep linking”
Exclude records that contain a specific term prefixed with a minus. e.g. Android -Firebase

iOS Troubleshooting

Common misconfiguration scenarios you may run into and how to resolve them.


This guide lists out some of the most common challenges we see customers run into when trying to integrate the Branch iOS SDK.

To integrate the Branch iOS SDK, follow the steps in our iOS SDK Basic Integration guide.


App Does Not Open

If your app is not opening when you click a Branch Deep Link, confirm that:

  1. The Branch iOS SDK has been integrated into your app successfully.
  2. Universal Links are enabled on the device (can only be disabled on iOS 9 and iOS 10). The iOS SDK Testing guide has steps on testing a Branch Deep Link, which will re-enable Universal Links on the device.
  3. No issues related to the actual creation of the Branch Deep Link.
  4. Your website is properly configured for Universal Links.

Link Does Not Pass Data

If Branch Deep Link data is not getting funneled to your app, confirm that:

  1. You are not having issues related to the app not opening.
  2. Your console logs are free of errors. To check this, you need to enable logging.

Deep Links Are Long

If you find that your Branch Deep Links are long, this is because the app cannot make a connection to the Branch servers.

However, these long Branch Deep Links will still open the app and pass data.

Deferred Deep Linking Issues

If deferred deep linking is broken, confirm that you have enabled NativeLink™.

Not doing so will cause deferred deep linking to be broken on devices with iOS 15+ installed and Private Relay enabled.

You can also test your deferred deep linking scenario with these steps.

Deep Link Routing Issues

If you're having issues with deep link routing, confirm that:

  1. You have followed the appropriate steps in our guide for navigating to content.
  2. You test the routing with the ?bnc_validate=true param.