Closed Willham12 closed 1 week ago
We also have this issue.
Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.
@sanduluca did you solve the issue ?
Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.
@sanduluca did you solve the issue ?
No. We still have the crashes. Seems that it comes from react native itself
Hello 👋, to help manage issues we automatically close stale issues.
This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?
This issue will be closed in 15 days if no further activity occurs.
Thank you for your contributions.
This is probably related to the View / Activity going away via some sort of user dismiss or not being ready in time - both (in this hypothesis) in a race with the code trying to access the View / Activity, such that when the code finally gets to the point where it wants to do something with the View / Activity it is null and causes the crash
This stack frame is the only place we have the ability to affect what happens next:
at io.invertase.notifee.NotifeeApiModule.requestPermission(NotifeeApiModule.java:267)
...if that line of code were wrapped in a try/catch and caught Exception
it would be possible to at least not crash, and if the API of the requestPermission call allowed for promise rejection then we could reject and expose the problem to your app calling code so you could handle it
A PR to do at least the catch + native log of the problem would be most welcome, if the API was already async with Promise going in then a reject of the promise would be fantastic as part of the PR as well.
Refer to https://github.com/facebook/react-native/issues/41077
"@notifee/react-native": "7.8.2" "react-native": "0.74.3",