Open valera-kytyzov opened 7 months ago
@valera-kytyzov I'm also having some trouble with Dynamic links, I was doing some more testing before opening a ticket. For me the issue is that the Dynamic link generated by Generate Current Link always created the exact same link no matter the screen you are in and also always diverts to root (home screen). I tried with both google assigned domain and custom domain. Doing some more testing before opening a ticket, but core issue could be the same (Link not directing to correct screen possibly related to link created state issue). Cheers mate
So how long does it usually take you guys to fix a bug?
Has your issue been reported?
Current Behavior
I'm setting up push notifications via Firebase Cloud Messaging with Dynamic Links.
I am sending a request as shown below:
Both Android and iOS devices receive the push notifications. On Android, tapping on the push notification opens the desired page. However, on iOS, tapping on a push notification does not trigger any action.
When I tap on a link in any messenger on iOS, the correct application page opens, indicating that the links are configured properly. Therefore, the issue seems to be with the processing of the push notification link.
When I send test push notifications from FlutterFlow, specifying the page to be opened and its parameter, everything works as expected: the page opens on both Android and iOS devices. This leads me to wonder if FlutterFlow composes the request for sending push notifications in a unique way?
Expected Behavior
I expected that upon tapping the push notification sent via Firebase Cloud Messaging with an attached Dynamic Link, the application would open the specified page on both Android and iOS devices.
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT4klsjfz81Oj7xH15CAbcJ4jSoUQlw8TL07ttYbZxUjIuPtBJh+Pc/eSFdBOP25TFNhHFX/mlsB+sLGiIflUfkFGEmqbJhi1bpqYALJf3q8R4S1C7mWdHJAJ+NbG0iv1MGRghYmNbJ1dV4k1GCHe+iXdHXDN5u/Zwh9f6PHaOI=
Context
I'm trying to make push notifications via FCM
Visual documentation
Additional Info
No response
Environment