Annoying UI Error

[quinb96]

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.25.2

Steps to reproduce the bug

Can't reproduce it. Happens randomly. However this happens A LOT.

Expected behavior

To simply just operate correctly and not spawn this error every 2 mins.

Actual behavior

Error comes up ALL THE TIME.
I've looked up this error and there doesn't seem to be a clear answer on why this comes up for many people so much. I'm not seeing that the Newpipe team had ever answered why this happens. I apologize but I've had enough of this error now. Is there a known permanent fix for this?

Screenshots/Screen recordings

No response

Logs

#10648

Affected Android/Custom ROM version

Android 13

Affected device model

Samsung Galaxy A13 5G

Additional information

Same issue described in #10648 but was closed without providing me any information that helps. What certain keywords do I need to be using? Can you link me to an issue that actually answers my questions? Otherwise this will just continue.

[Nes2525]

Try new version, maybe it will go away. v0.26

[31duderino]

And here I thought it was just me:

Exception

• User Action: ui error
• Request: ACRA report
• Content Country: US
• Content Language: en-US
• App Language: en_US
• Service: none
• Version: 0.25.2
• OS: Linux Android 14 - 34

Crash log

android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{55aa30c u0 org.schabi.newpipe/.player.PlayerService}
	at android.app.ActivityThread.generateForegroundServiceDidNotStartInTimeException(ActivityThread.java:2104)
	at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2075)
	at android.app.ActivityThread.-$$Nest$mthrowRemoteServiceException(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2369)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:205)
	at android.os.Looper.loop(Looper.java:294)
	at android.app.ActivityThread.main(ActivityThread.java:8177)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971)
Caused by: android.app.StackTrace: Last startServiceCommon() call for this service was made here
	at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1952)
	at android.app.ContextImpl.startForegroundService(ContextImpl.java:1906)
	at android.content.ContextWrapper.startForegroundService(ContextWrapper.java:830)
	at android.content.ContextWrapper.startForegroundService(ContextWrapper.java:830)
	at androidx.core.content.ContextCompat$Api26Impl$$ExternalSyntheticApiModelOutline1.m(R8$$SyntheticClass:0)
	at androidx.core.content.ContextCompat$Api26Impl.startForegroundService(ContextCompat.java:1091)
	at androidx.core.content.ContextCompat.startForegroundService(ContextCompat.java:749)
	at androidx.media.session.MediaButtonReceiver.onReceive(MediaButtonReceiver.java:115)
	at android.app.ActivityThread.handleReceiver(ActivityThread.java:4449)
	at android.app.ActivityThread.-$$Nest$mhandleReceiver(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2256)
	... 7 more

---

Affected Android/Custom ROM version
Android 14

Affected device model
Pixel 7 Pro

[Nes2525]

Also make sure newpipe excluded from battery optimization.

[quinb96]

Try new version, maybe it will go away. v0.26

This has been an issue with different devices for literally over a year. I'm almost certain that specific version won't fix this.

App is unrestricted in battery optimization. I've downloaded this app from F-droid and here on Github and used previous versions as well. I've deleted cache, deleted data, tried an app called PipePipe which has the exact same issue as Newpipe. I'm sorry if I sound rude but I genuinely think no one is doing anything about this error. If so, I do apologize but this error plagues this app.

[quinb96]

And here I thought it was just me:

Exception

• User Action: ui error
• Request: ACRA report
• Content Country: US
• Content Language: en-US
• App Language: en_US
• Service: none
• Version: 0.25.2
• OS: Linux Android 14 - 34

Crash log

android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{55aa30c u0 org.schabi.newpipe/.player.PlayerService}
	at android.app.ActivityThread.generateForegroundServiceDidNotStartInTimeException(ActivityThread.java:2104)
	at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2075)
	at android.app.ActivityThread.-$$Nest$mthrowRemoteServiceException(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2369)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:205)
	at android.os.Looper.loop(Looper.java:294)
	at android.app.ActivityThread.main(ActivityThread.java:8177)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971)
Caused by: android.app.StackTrace: Last startServiceCommon() call for this service was made here
	at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1952)
	at android.app.ContextImpl.startForegroundService(ContextImpl.java:1906)
	at android.content.ContextWrapper.startForegroundService(ContextWrapper.java:830)
	at android.content.ContextWrapper.startForegroundService(ContextWrapper.java:830)
	at androidx.core.content.ContextCompat$Api26Impl$$ExternalSyntheticApiModelOutline1.m(R8$$SyntheticClass:0)
	at androidx.core.content.ContextCompat$Api26Impl.startForegroundService(ContextCompat.java:1091)
	at androidx.core.content.ContextCompat.startForegroundService(ContextCompat.java:749)
	at androidx.media.session.MediaButtonReceiver.onReceive(MediaButtonReceiver.java:115)
	at android.app.ActivityThread.handleReceiver(ActivityThread.java:4449)
	at android.app.ActivityThread.-$$Nest$mhandleReceiver(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2256)
	... 7 more

---

Affected Android/Custom ROM version
Android 14

Affected device model
Pixel 7 Pro

There's a lot of people having this issue at least from the research I've done. I'm not seeing that there was ever a permanent fix for this discovered for this. If there's a perament fix out there please link us to that fix.

[Stypox]

This was a duplicate of tens of issues (e.g. #9030, you could have just searched for them before opening a duplicate...), has already been fixed in #10578 and the upcoming 0.26.0 will contain the fix (you can use the APK on top of #10471). Next time follow the suggestions you are given, instead of repeatedly opening duplicate issues and saying things like "I'm almost certain that specific version won't fix this." without even trying.

[quinb96]

This was a duplicate of tens of issues (e.g. #9030, you could have just searched for them before opening a duplicate...), has already been fixed in #10578 and the upcoming 0.26.0 will contain the fix (you can use the APK on top of #10471). Next time follow the suggestions you are given, instead of repeatedly opening duplicate issues and saying things like "I'm almost certain that specific version won't fix this." without even trying.

But this is probably my 3rd to 4th time saying I had extensively looked through all that and I couldn't find it. Everyone keeps telling me that but it appears to me you guys aren't even thoroughly reading what I'm saying or not understanding. I don't know how else to express I've done extensive troubleshooting. Then asked maybe 3 times for someone to link me to issues that may solve my problem. You're the first one to do anything of the sort. I said more than once if there's a fix and I'm not seeing it then please link me. No one wanted to do that. So idk. Also for assuming that 0.26.0 wouldn't work, it may be wrong for me to assume it won't work but at the same time this has been an issue for me for idk how many versions now so you can't entirely blame me for assuming that.

[quinb96]

This was a duplicate of tens of issues (e.g. #9030, you could have just searched for them before opening a duplicate...), has already been fixed in #10578 and the upcoming 0.26.0 will contain the fix (you can use the APK on top of #10471). Next time follow the suggestions you are given, instead of repeatedly opening duplicate issues and saying things like "I'm almost certain that specific version won't fix this." without even trying.

And I keep being told there's tens of the same thing. OK and I see that. That's a clear indication of a serious bug. it appeared to me that no one was trying to fix the issue. If so, that's great but no one had the incentive to actually link me to that info to show me that. I'm not sure why you guys are expecting us to just stop reporting this. The only way I see people stop reporting this if the error was truly resolved on 0.26.0.

[opusforlife2]

I've done extensive troubleshooting

I understand the feeling, but unfortunately that is not enough. You have to work with the maintainers of the project you're participating in, even if that sometimes means repeating steps or doing things you're sure won't work. The maintainers don't know your brain, nor can they telepathically glean all your activities regarding the bug.

But if you come out the door guns blazing, flinging your frustration around at everyone else, then it makes for a very difficult interaction no matter what project you're in.

FYI, when I told you to search using the string I provided from your crash log, it would have led you to discover exactly what Stypox showed, that there are dozens of duplicate reports about the same thing. You just happened to give up at that exact step.

Moreover, a general policy of reporting bugs in any software project is to test the latest version available, including release candidates, nightlies, beta versions, etc. If you had tested the RC, you wouldn't have had to open an issue at all.

[quinb96]

I've done extensive troubleshooting

I understand the feeling, but unfortunately that is not enough. You have to work with the maintainers of the project you're participating in, even if that sometimes means repeating steps or doing things you're sure won't work. The maintainers don't know your brain, nor can they telepathically glean all your activities regarding the bug.

But if you come out the door guns blazing, flinging your frustration around at everyone else, then it makes for a very difficult interaction no matter what project you're in.

FYI, when I told you to search using the string I provided from your crash log, it would have led you to discover exactly what Stypox showed, that there are dozens of duplicate reports about the same thing. You just happened to give up at that exact step.

Moreover, a general policy of reporting bugs in any software project is to test the latest version available, including release candidates, nightlies, beta versions, etc. If you had tested the RC, you wouldn't have had to open an issue at all.

I apologize for the frustration. It's due to this error happening every 2 mins in combination with believing that the team will not do anything about it. I sometimes won't even be touching my phone and this error would come up.. And I did search open and closed issues but I was seeing either no one actually knew what the problem was and so it just gets closed unresolved, or the phone had no more RAM. If the problem wasn't the phone being too low on RAM, no one seemed to know what the issue was then. And I'm seeing that this has been a problem for months now. Since this became an issue at least for me which has now been over a month ago, I recall a few updates being released since then and none of them are even aimed to fix this issue. So then this made me think that you guys know this is an issue and deliberately won't fix it. Then telling me to search issues after I've done that A LOT only made me more frustrated. I've almost decompiled the APK just to see if I can find the issue cause I know it's a Java error but just too lazy to do so.

[opusforlife2]

Many of my friends have regularly faced this issue as well. I've given them all the latest RC with the fix, even though you normally let users update from one stable release to the next. So I know how annoying the issue is.