Skip to content
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

Synerise notification's deeplink is handled only after resume #14

Closed
tmaxxdd opened this issue Sep 27, 2024 · 14 comments
Closed

Synerise notification's deeplink is handled only after resume #14

tmaxxdd opened this issue Sep 27, 2024 · 14 comments

Comments

@tmaxxdd
Copy link

tmaxxdd commented Sep 27, 2024

During implementation of sdk version 1.3.1. We have noticed on Andrioid that there is a specific case when clicking on the notification in foreground the action is not invoked immediately but after resume (back from background)

The reproduction of error in example app:

deeplink_launch_after_resume.mov
@konned
Copy link
Collaborator

konned commented Sep 27, 2024

Thanks, we are investigating this issue. I will let you know soon.

@tmaxxdd
Copy link
Author

tmaxxdd commented Sep 27, 2024

Thank you

@tmaxxdd
Copy link
Author

tmaxxdd commented Oct 8, 2024

@konned It is possible to estimate how long does it take to prepare a fix?

@konned
Copy link
Collaborator

konned commented Oct 8, 2024

We are in a final part of testing. Max 1-2 days to new release.

@tmaxxdd
Copy link
Author

tmaxxdd commented Oct 8, 2024

Thank you really much for the instant reply

@tmaxxdd
Copy link
Author

tmaxxdd commented Oct 10, 2024

Should we check the new 1.4.0 version?

@konned
Copy link
Collaborator

konned commented Oct 10, 2024

Yeap, Sorry I forgot to inform you yesterday.

@tmaxxdd
Copy link
Author

tmaxxdd commented Oct 10, 2024

Okay, I started implementing new version yesterday. Did you check the fix on the example app?

@tmaxxdd
Copy link
Author

tmaxxdd commented Oct 11, 2024

@konned I asked bc in our product using 1.4.0 this error still exists

@konned
Copy link
Collaborator

konned commented Oct 11, 2024

Yes, unfortunately we did not upgrade native sdk by a mistake. Version with a fix will be released during weekend.

@tmaxxdd
Copy link
Author

tmaxxdd commented Oct 11, 2024

Okay, thank you for response

@konned
Copy link
Collaborator

konned commented Oct 14, 2024

Hi, In 1.4.1 everything should work fine ;)

@tmaxxdd
Copy link
Author

tmaxxdd commented Nov 12, 2024

@konned We have no issues for now so I assume you can close this issue

@awoczek
Copy link
Collaborator

awoczek commented Nov 12, 2024

@tmaxxdd thank you for your feedback and help!

@awoczek awoczek closed this as completed Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants