[Bug]: Deeplink not working if the app is closed

[cgmleadtech]

What happened?

I have some deep links set up and if I manually click them, they work, but if I receive the link in the notification and the app is closed, they don't, if the app is open the deep links work when clicking the notification.

Example link: myapp://test

APP is open (Foreground, background)

• Manually click the link -> OK
• Click on a notification with the link -> OK

APP closed

• Manually click the link -> OK
• Click on a notification with the link -> KO

---

This is how I send a test notification:

This is what I mean by Manually clicking a link

Steps to reproduce?

1. Initialize OneSignal (Install the app, etc...)
2. Accept permissions
3. Send test notification to the user with deep link
4. Open it
5. works
6. Close the app
7. Send the notification again
8. Open it
9. Does not work

What did you expect to happen?

I would expect that both clicking on the link locally and clicking in the notification did the same

OneSignal Flutter SDK version

5.0.0

Which platform(s) are affected?

• iOS
• Android

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[emawby]

Thank you for reporting #741 and this issue seem to be related (opening notifications when the app is closed). We are investigating.

[ariona]

I tried to revert back to onesignal_flutter 3.5.1, but no luck, on iOS, clicking notification to open deeplink is not working.

So i think it's not related to latest version (5.0.1), rather than data changes when sending notification @emawby

[alegos27]

any update? it seems to be releted to #723

[emawby]

@alegos27 Hello we are still working on the fix. It requires a change to our OneSignal-iOS-SDK that has been approved and will be released asap!

[alegos27]

Any news about it? We saw 5.0.2 version of iOS SDK but the Flutter SDK has no updates and the bug still remain.

[emawby]

@alegos27 The next OneSignal-Flutter-SDK release will bump the dependnecy to use the 5.0.2 version of the iOS SDK and will include the fix for this

[indrian16]

Finally, version 5.0.2 is out, and this issue has been resolved. I just tested it, thank you @emawby