-
Notifications
You must be signed in to change notification settings - Fork 4k
[firebase_dynamic_link] v0.5.0 is not correctly working in ios in running/background state #1124
New issue
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
Comments
The issue at flutter/flutter#38744 has been closed and moved here. Future collaboration on this issue will be done here. |
Here are my findings on that issue. FirebaseDynamicLinks.instance.getInitialLink() returns null in the following situations:
It only works when app is in foreground mode. All tests with the same DynamicLink and URL clicked from Notes app on iOS Xr real device. So from what i can gather, its totally unusable at this point. Redirecting to AppStore works without problem if the app is not installed at all. Tested with:
used firebase_dynamic_links: ^0.5.0+1 together with: Flutter (Channel dev, v1.10.14, on Mac OS X 10.15 19A583, locale de-DE) |
To buttress @logemann's findings, it always works on iOS when the app is in the foreground mode. However, it works for me in background mode, but it appears to be random and inconsistent. |
I got the same behaviour with 0.4.0+6, also. |
Nevermind. Got it working just like it should. All having this same issue, please follow the setup guide on the flutter pub site.
|
Seems like in general this issue is resolved. For more specific cases where there are issues with the plugin please file an issue. |
In android application firebase dynamic link 0.5.0 is working fine. But in ios device dynamic link is not working when app is in running/background state. But in killed state it works fine means when link is clicked in killed state it open correct location in the application.
I have no idea why it is happening.
should I use one of the old versions?
The text was updated successfully, but these errors were encountered: