Bouncy deeplinks can be configured to open a specific mobile app when clicked. If the link is not opening the app as expected, there are several factors that could be causing the issue.

How App Deeplinks Work

When a user clicks a Bouncy deeplink configured for app opening:

The link checks whether the target app is installed on the user's device.
If the app is installed, it opens the app to the specified screen or content.
If the app is not installed, it falls back to a web URL (typically the app store page or a landing page).

Common Causes and Solutions

1. The App Is Not Installed

Symptom: The link opens a web page or app store instead of the app.

Solution: This is expected behaviour. If the target app is not installed on the user's device, the link will redirect to the fallback URL. Make sure your fallback URL points to a useful destination, such as the App Store or Google Play page for the app.

2. Incorrect App Link / URI Scheme

Symptom: The link opens in the browser instead of the app, even though the app is installed.

Solution: Check that your deeplink is configured with the correct app link parameters:

For iOS: Verify your Universal Link domain and path.
For Android: Verify your App Links configuration.
For URI schemes: Ensure the scheme (e.g., myapp://) is correctly set.

3. Social Media In-App Browsers

Symptom: The link opens in an in-app browser (within Instagram, Facebook, Twitter, etc.) instead of launching the app.

Solution: Many social media platforms open links in their own built-in browser, which often does not support app deeplinks. Bouncy handles this by displaying an intermediate page that gives the user a button to open the link in their device's default browser. This is expected behaviour and is a workaround for platform limitations.

4. Platform Restrictions

Symptom: Links work on one platform (iOS or Android) but not the other.

Solution: App deeplinks may need separate configuration for iOS and Android. Check your deeplink settings to ensure both platforms are configured. iOS uses Universal Links, while Android uses App Links -- each requires specific setup on the app developer's side.

5. App Not Configured for Deeplinks

Symptom: The app opens but does not navigate to the correct screen or content.

Solution: The app itself must be configured to handle the deeplink URL. This is an app-side configuration issue. Work with the app developer to ensure the app handles incoming deeplink URLs correctly.

6. Browser or OS Blocking the Redirect

Symptom: A popup or security warning appears instead of the app opening.

Solution: Some browsers and operating systems have security measures that prevent automatic app launching. The user may need to tap a confirmation button or adjust their device settings.

Testing Tips

Test on a real device -- App deeplinks often do not work correctly in browser developer tools or emulators.
Test both platforms -- Verify on both iOS and Android devices.
Test with the app both installed and uninstalled -- Confirm that the fallback behaviour works correctly.
Test from different sources -- Try clicking the link from a text message, email, browser, and social media to see how each handles it.
Clear the app's default link settings -- On Android, go to Settings > Apps > [App name] > Open by default, and clear any existing preferences.