Open almantas88 opened 1 year ago
How come this field is required? I was unable to leave it unchecked.
Also I saw this text in the FF documentation explaining how the dynamic link should work.
Dynamic Link The dynamic link opens a specific page in your app. Unlike the deep link, the dynamic link survives the app install. That means if the user has not installed the app, they can be taken to the respective store to install the app. After the app is installed, users can be taken straight to the intended app page.
Same here,
this a blocker bug for my project (https://app.flutterflow.io/project/toigram-emnkaa), I think it used to work few weeks ago, but suddenly discovered this is not working yesterday.
Thanks for support, FF team!
Hi @almantas88 - Thanks for submitting the issue. I can reproduce the issue. Above given dynamic app link, I can see iOS can navigate the app but not taking to the page.
Hello! any progress/workarounds available?
Any update?
???
This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.
FF team! Any updates?
yeah, any update would be amazing...
This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.
I am having the same issue and its killing my app. Would love some help here. We are actively working to integrate Branch.io but would love to use flutterflows dynamic links in the future.
Any updates? Not only does the dynamic link not survive the install and first load but it also crashes the router. So routing is broken - app needs to be force closed. Causing a horrible for experience for our users.
Hello, I wanted to provide an update regarding the issue we were experiencing with Firebase Dynamic Links in our app. After some investigation and troubleshooting, I was able to resolve the problem by switching to Branch.io for deep linking. I'm pleased to share that the transition to Branch.io has been successful, and our deep linking functionality is now working smoothly. Here's an outline of the steps involved:
Note: You can achieve this transition entirely from GitHub without the need for Xcode.
Feel free to reach out if you have any questions or need further guidance. I'm confident that this solution will greatly enhance our app's deep linking capabilities.
Hello, I wanted to provide an update regarding the issue we were experiencing with Firebase Dynamic Links in our app. After some investigation and troubleshooting, I was able to resolve the problem by switching to Branch.io for deep linking. I'm pleased to share that the transition to Branch.io has been successful, and our deep linking functionality is now working smoothly. Here's an outline of the steps involved:
- Export your code to GitHub using FlutterFlow's documentation.
- Modify the following files in your project: • android/app/build.gradle • android/app/src/main/AndroidManifest.xml • ios/Runner/Info.plist • ios/Runner/Runner.entitlements • lib/main.dart
- Additionally, add a new file named lib/branch_handler.dart to your project.
- Create a Branch.io account and set it up.
Note: You can achieve this transition entirely from GitHub without the need for Xcode.
Feel free to reach out if you have any questions or need further guidance. I'm confident that this solution will greatly enhance our app's deep linking capabilities.
But this way you can't go back to FF editor and also it removes the ability to deploy via codemagic
@agreaves @SameerShahzad99 any updates on this issue?
@almantas88 actually you can still build in flutterflow and you can still deploy using code magic. The only difference is you have to first merge your flutterflow changes with the develop and main branch in github.
also the branch.io links work super well and have a ton of added benefits that i didn't even know existed.
@agreaves It would be awesome if branch.io was integrated with flutterflow so we didn't have to make these changes in github. Firebase dynamic links not survive ios download and they also break the push notificaion navigation sometimes.
Hello, I apologize for the late reply. Does this issue still persist? We had a related issue that was resolved a few weeks ago, and I hope it has fixed this issue. Thank you for your patience.
Hi @takashiff, the issue still persists, and we need it fixed please
I just tried a new iOS build. The dynamic link leads to a TestFlight install which is great, and the routing/clicks work, but it does not pass me the link data. After the app has been installed and I click the link, it passes me the link data.
When it installs the Android version of the app, it passes the link data.
Please try to reproduce this, I dont think it is application specific, but it is iOS specific.
Has your issue been reported?
Current Behavior
When I open a dynamic link on iOS device when the app is not install, the dynamic link doesn't survive the install. I do not get redirected to expected page. On the Android it works as expected, it survives the app install and opens the intended screen.
Here is the link: https://sxlife.page.link/?ofl=https://sx.life/&apn=com.mycompany.sxlife&ibi=com.mycompany.sxlife&isi=6450038292&imv=Z8BS4W7LA8&link=https%3A%2F%2Fsxlife.page.link%2FacceptInvite%2FW3TpQF2qNEggWVGUh6x7jjKKi%2Falmantas+neda@idealink.tech
Expected Behavior
The dynamic link should survive the app install and redirect to a specific page, with some data in the url.
Steps to Reproduce
Use iOS for bug, use android for expected behavior;
Reproducible from Blank
Bug Report Code (Required)
IT4OjMmAvJF2rtdc15P2de9agmQXNmYiU4ZMkMJxawE3COLNGu4Iec/eUFZuZr3nS29IMGKguH8J/PfqveH9DcI5NTmbGbo+wc5pWxWXRkKhRYuVPIe7fW1QAd5QCHKa37WJhyJDPthuLngn1zuIOOyRHwjZGbqwOW4jIcq1JdeK2SrDX1iXc2URm05KZDPz
Context
It is one of the main functionalities for users. As this app is live, a lot of users writing to our support about this issue;
Visual documentation
iOS: https://github.com/FlutterFlow/flutterflow-issues/assets/47143702/31bc6767-602a-492f-9bd0-a6041f27b538
Android: https://github.com/FlutterFlow/flutterflow-issues/assets/47143702/94b555cb-0032-4796-a967-f91c85dd1bab
Additional Info
No response
Environment