FlutterFlow / flutterflow-issues

A community issue tracker for FlutterFlow.
127 stars 26 forks source link

Navigation is not working with dynamic links #2202

Open MadhurNarangGithub opened 9 months ago

MadhurNarangGithub commented 9 months ago

Has your issue been reported?

Current Behavior

The navigation actions on button is not working when I open the IOS app using dynamic links but in android they work fine.

Expected Behavior

All the actions in the IOS app should work fine , even if user opens the app through dynamic links

Steps to Reproduce

Pre-requisite - Your app page should have a navigation action

  1. Enable deep linking through firebase.
  2. Create a dynamic link for the app page
  3. Open the app using the link

Reproducible from Blank

Bug Report Code (Required)

IT4kysn12It2octJ0Lrfbe4wpDg7OVx6TLJEoetxc0gbfe/4PbAufPTCTBBVYOazaH5EAGH8uHIEwNaJvoTyUPZdGwuVQKY/1qt6WBPPbGq7VYS7PauoYXBPN95Uf2qa5sO3mCZ/LbF2cU5n6kOyetzLbz6Cf9qOYwx5e6fDbOY=

Context

Trying to build a referral link in our app , so when user clicks on it the referral code on complete profile page is pre-populated. But because of this issue app is stuck on login screen and I am not able to create a referral system for my app

Visual documentation

All the actions till api call are working fine , except the navigation action.

actions on button

login page settings

Additional Info

Scenarios tried for troubleshooting -

  1. Open the link from any social media app - Navigation action not working!
  2. Open the link by entering it into browser - App is working fine.
  3. Write custom code for navigation - Navigation action not working!
  4. Isolate the navigation action have no other action - Navigation action not working!
  5. Redirect to the login page again if refCode is present to kind-a-surpass the coldboot of IOS - Navigation action not working!

Possible Reason - There is a permission screen which is shown when I try to open the link from browser but when I try to open it from any other apps that screen is not shown and I am redirected to the app directly.

Another scenario - IF I directly use the deep link https://redirect.getyield.in/{page route} i.e https://redirect.getyield.in/login then this works fine in IOS but in android it shows error that dynamic link not found. (as I did not setup this dynamic link in firebase)

Attaching all other

https://github.com/FlutterFlow/flutterflow-issues/assets/148282402/99a8467d-3301-405b-8a44-cf75a4577a32

https://github.com/FlutterFlow/flutterflow-issues/assets/148282402/144f4658-019b-4be1-a769-0c6e0686f5af

permission screen (only from browser)

dynamic link details

Environment

- FlutterFlow version: 3.13.7
- Platform:Web
- Browser name and version:Brave Version 1.61.120 Chromium: 120.0.6099.234 (Official Build) (64-bit)
- Operating system and version affected: IOS 17.2.1
MartinLockheart commented 9 months ago

Adding on here, I've had this issue for a few weeks as well.

MadhurNarangGithub commented 9 months ago

Adding on here, I've had this issue for a few weeks as well.

@MartinLockheart you find any workaround for this ?till it is fixed by flutterflow

SEGVeenstra commented 9 months ago

This might be related to the problem I've been having for months now. https://github.com/FlutterFlow/flutterflow-issues/issues/1697#issuecomment-1788639011

We use dynamic link for email-link signin. So:

  1. The user fills out their email in the app
  2. Email is send to user with signin link.
  3. User clicks link in email
  4. App opens and signs in user.

At this point the navigation is not working. Every call to the go_router is ignored.

What I did notice on Android is that when you click the email link, and the app opens, it doesn't open the same instance, it's creating a new instance of the app. If I close that one, and go back to the first instance, it is also been signed-in, but there the navigation is working.

github-actions[bot] commented 8 months ago

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.

github-actions[bot] commented 8 months ago

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.

github-actions[bot] commented 6 months ago

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.