Setup Deep Link
Deep linking allows users to open specific content in your eBroker app directly from links in websites, emails, or messages. This guide explains how to set up deep linking for your application.
Admin Panel Side Configuration
- Add Deep Link schema:
- In the admin panel, navigate to the
Settings > System Settings
section. - Find the "Deep Link Settings" section.
- Under "Schema" add your desired schema.
- In the admin panel, navigate to the
App Side Configuration
note
Choose the appropriate domain based on your usage:
- If using a web domain, add the web domain. (If you want to use web for redirect)
- If using a panel domain, add the panel domain.
- Update
settings.dart
:- Open
lib > settings.dart
. - Update the
shareNavigationWebUrl
variable with the domain that you are using for deeplink.
- Open
- Update for Android:
- Open
android > app > src > main > AndroidManifest.xml
. - In your
AndroidManifest.xml
file, Update the following with schema you added in admin panel and domain you added in settings.dart:
- Open
- Update for iOS:
-
Open
ios > Runner > Info.plist
. -
In your
info.plist
file, update the following same as schema you added in admin panel:<key>CFBundleURLSchemes</key>
<array>
<string>your_schema</string>
</array>
```:
-
How Deep Links Work
When a user clicks a deep link:
- The link opens your app if it's installed
- The app navigates to the specific content referenced in the link
- If the app isn't installed, the link can direct the user to the app store
Testing Deep Links
After setting up deep links:
- Create a test link in the format:
https://yourdomain.com/link_path
- Send this link to a device with your app installed
- Click the link and verify that it opens the correct content in your app
Troubleshooting
If deep links aren't working:
- Verify that the
.well-known
folder and its files are accessible via browser - Ensure the
.htaccess
file is properly configured - Check that your app's build configuration correctly includes the deep link handling code
- Test on multiple devices to rule out device-specific issues