-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[bug] android.app.ForegroundServiceStartNotAllowedException: startAndStopEmptyNotificationToAvoidANR #2184
Comments
we have the same problem on android 14. :( |
seems very similar to the flutter folks experiencing, related to battery optimization |
Hi everyone, just wanted to kindly ask you if you made any progress on this issue, thanks in advance. |
I’m seeing the exact same crash reports while using version 4.0.1 |
Also happening on prod using > "react-native-track-player": "^3.2.0-7b02a2d2a51370819b91ea8da1fe835a617c3199",
|
track-player 4.0.1 - [ google husky (Pixel 8 Pro) ] - [ Android 14 (SDK 34) ]
|
Just got same on Pixel 7 on Android 14 |
Also seeing this with v4.0.1 — any thoughts on cause, workaround? EDIT: I just released an app update that uses TrackPlayer and:
|
ping - anythoughts? |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Not stale, still happening frequently. Just haven’t had time to investigate further yet. |
any solution for this folks ? |
This is still an issue AFAIK, @nateshmbhat I'm sure the maintainers would welcome a PR! Our best guess so far as to the scenario under which this occurs:
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Still an issue with 4.1.1 |
i might have a better understanding about this error. this is thrown when
playback is not started as the service is, so the whole empty notif
workaround is used. the exact case when this happens is atartService in
MusicModule. my educated guess now is the service is being restarted for
whatever reason.
from what ive seen recently, media3 migration might help, as then service
handling is largely handled by the lib itself
…On Sun, Oct 6, 2024, 8:28 PM Elliot Dickison ***@***.***> wrote:
Still an issue with 4.1.1
—
Reply to this email directly, view it on GitHub
<#2184 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZMOVVUD5AOIMJXD4AB7Z2LZ2H5XHAVCNFSM6AAAAAA6MZ7BVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVHAZDCNZTGQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Describe the Bug
We recently released
3.2.0-b13a92208eaf9607a12cfa7596dfa6ae4f4a4c8e
into production to take advantage of some of the updated Android foreground service logic (thank you!). We saw the long-timeandroid.app.ForegroundServiceStartNotAllowedException
bug disappear completely (woohoo!) but this one started popping up at about the same frequency. The issue only occurs in the background. This seems closely related to #1986, but per the discussion on that issue I'm opening a new issue.Steps To Reproduce
We have yet to reproduce locally on our devices. We have tried forcing the device into doze mode, loading new tracks in the background, playing for extended periods of time, etc. The issue is happening with regular frequency in production with an install base of ~6K
Code To Reproduce
Use
3.2.0-b13a92208eaf9607a12cfa7596dfa6ae4f4a4c8e
Replicable on Example App?
We have yet to reproduce the issue even in our app, once we do we'll check the example app.
Environment Info:
react-native-track-player@3.2.0-b13a92208eaf9607a12cfa7596dfa6ae4f4a4c8e
How I can Help
What can you do to help resolve this?
Have you investigated the underlying JS or Swift/Android code causing this bug?
Can you create a Pull Request with a fix?
The text was updated successfully, but these errors were encountered: