-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Description
Checklist
- I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
- I made sure that there are no existing issues - open or closed - which I could contribute my information to.
- I have read the FAQ and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected version
0.28.0
Steps to reproduce the bug
Caveat
I have been unable to 'reproduce' as it has been persistent across a
- reboot
- cache/storage clear
- uninstall/reinstall.
It is now persistent. I'm assuming there are some files in my accessible directories I will need to clear to attempt to recreate.
Steps
- Select a video
- Download the audio
- Accidentally set the threads to a number higher than your phone supports. (My Pixel 8 Pro supports 9, and I accidentally set it to 13)
- After trying to navigate the interface, an error prompt pops repeatedly (specifically 4 times, it appears for the 4 threads above my supported thread count),
- Upon restart of the app, it appears to try to resume the download with the set number of threads, and subsequently repeats step 4.
Expected behavior
If the threads are higher than what the device supports, throw an error and prevent the download, or silently only use max available.
If the download job fails, cancel, and not loop on repeat making the app unusable.
Actual behavior
See steps to reproduce
Screenshots/Screen recordings
Only error screen, no screenshot
Logs
Exception
- User Action: ui error
- Request: ACRA report
- Content Country: US
- Content Language: en-US
- App Language: en_US
- Service: none
- Timestamp: 2025-10-08T16:00:31.699-05:00
- Package: org.schabi.newpipe
- Service: none
- Version: 0.28.0
- OS: Linux Android 16 - 36
Crash log
android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{9ff41e4 u0 org.schabi.newpipe/.player.PlayerService c:org.schabi.newpipe}
at android.app.ActivityThread.generateForegroundServiceDidNotStartInTimeException(ActivityThread.java:2404)
at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2372)
at android.app.ActivityThread.-$$Nest$mthrowRemoteServiceException(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2748)
at android.os.Handler.dispatchMessage(Handler.java:110)
at android.os.Looper.dispatchMessage(Looper.java:315)
at android.os.Looper.loopOnce(Looper.java:251)
at android.os.Looper.loop(Looper.java:349)
at android.app.ActivityThread.main(ActivityThread.java:9041)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:593)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)
Caused by: android.app.StackTrace: Last startServiceCommon() call for this service was made here
at android.app.ContextImpl.startServiceCommon(ContextImpl.java:2049)
at android.app.ContextImpl.startForegroundService(ContextImpl.java:2003)
at android.content.ContextWrapper.startForegroundService(ContextWrapper.java:860)
at android.content.ContextWrapper.startForegroundService(ContextWrapper.java:860)
at androidx.core.content.ContextCompat$Api26Impl.startForegroundService(ContextCompat.java:1128)
at androidx.core.content.ContextCompat.startForegroundService(ContextCompat.java:700)
at androidx.media.session.MediaButtonReceiver.onReceive(MediaButtonReceiver.java:120)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:5090)
at android.app.ActivityThread.-$$Nest$mhandleReceiver(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2584)
... 8 more
Affected Android/Custom ROM version
Android 16 - 36
Affected device model
Pixel 8 Pro
Additional information
Any comments on which directory I could clear that has the download queue that in my head is potentially the trigger, as that didn't seem to be deleted with the uninstall or cache/storage clear, which makes me think it lives in the user directories somewhere, and I may have to delete/edit to get app functionality back. I assume this as I was able to see my saved lists when navigating quickly before the app crashes again.
This is my first bug for this repo, I did try to ensure that it was not a repeat, so I apologize if I missed any terminology in my search that may have been a repeated issue.