We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm using https scheme and am testing on my iPhone 8 device which is running iOS 15.6
This is my Runner.entitlements:
Runner.entitlements
<key>com.apple.developer.associated-domains</key> <array> <string>applinks:ALIAS.APPNAME.pl</string> <string>applinks:share.APPNAME.pl</string> </array> <key>FirebaseDynamicLinksCustomDomains</key> <array> <string>https://share.APPNAME.pl</string> <string>https://ALIAS.APPNAME.pl</string> </array> <key>FlutterDeepLinkingEnabled</key> <true/>
My Info.plist:
<key>CFBundleURLTypes</key> <array> <dict> <key>CFBundleTypeRole</key> <string>Editor</string> <key>CFBundleURLName</key> <string>ALIAS.APPNAME.pl</string> <key>CFBundleURLSchemes</key> <array> <string>http</string> <string>https</string> <string>ALIAS</string> </array> </dict> </array>
My Firebase Dynamic Link configuration looks like this:
And I try opening a url looking like this: https://ALIAS.APPNAME.pl/?offerId=2137
on Android it works perfectly fine, but on iOS it doesn't work (opens browser instead of the installed app/appstore page).
The text was updated successfully, but these errors were encountered:
@dawid-niedzwiecki Have you found a solution?
Sorry, something went wrong.
No branches or pull requests
I'm using https scheme and am testing
on my iPhone 8 device
which is running iOS 15.6
This is my
Runner.entitlements
:My Info.plist:
My Firebase Dynamic Link configuration looks like this:
And I try opening a url looking like this:
https://ALIAS.APPNAME.pl/?offerId=2137
on Android it works perfectly fine, but on iOS it doesn't work (opens browser instead of the installed app/appstore page).
The text was updated successfully, but these errors were encountered: