This repository has been archived by the owner on Oct 6, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 266
Context.startForegroundService() did not then call Service.startForeground() #393
Labels
Comments
+1 |
2 similar comments
+1 |
+1 |
Anyone able to investigate and provide some more insight or bug fixes/PRs? |
my code worked fine on android 8.1.0, but got the same issue on android 9/10 devices. any update ? |
Happening on OnePlus 8T with Android 12. |
Fixed by adding notification permissions, it's my fatal... |
@fandypeng could you share your solution? |
Still the same issue on an Expo client. Crashes 5 seconds after opening the notification as hinted here. I did not specify a "permission" key in app.json so that the Stack trace
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Related #266
Version v1.4.0 (latest)
Description
I am experiencing this error on production, but it seems that it only happens to Samsung devices according to BugSnag and when they close the app.
Sample code (provide repo url or sample code)
Platform ?
Device
The text was updated successfully, but these errors were encountered: