Had Enough of 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 their 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

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 13 - 33

Crash log

android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{c7666df u0 org.schabi.newpipe/.player.PlayerService}
	at android.app.ActivityThread.generateForegroundServiceDidNotStartInTimeException(ActivityThread.java:2245)
	at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2216)
	at android.app.ActivityThread.-$$Nest$mthrowRemoteServiceException(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2508)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:226)
	at android.os.Looper.loop(Looper.java:313)
	at android.app.ActivityThread.main(ActivityThread.java:8762)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
Caused by: android.app.StackTrace: Last startServiceCommon() call for this service was made here
	at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1988)
	at android.app.ContextImpl.startForegroundService(ContextImpl.java:1933)
	at android.content.ContextWrapper.startForegroundService(ContextWrapper.java:839)
	at android.content.ContextWrapper.startForegroundService(ContextWrapper.java:839)
	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:4894)
	at android.app.ActivityThread.-$$Nest$mhandleReceiver(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2420)
	... 7 more

---

Affected Android/Custom ROM version

Android 13

Affected device model

Samsung Galaxy A13 5G

Additional information

I've had this issue with multiple devices. I think that at least rules out it's not related to the phone model or OS.

[quinb96]

This version is from Github but the F-droid version is always spawning some different error.

[AudricV]

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.

You didn't, your issue is a duplicate of multiple closed ones. Please search (better, with different keywords?) for duplicates and use a better title than Had Enough of UI Error the next time you want to open an issue. Thank you.

[quinb96]

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.

You didn't, your issue is a duplicate of multiple closed ones. Please search (better, with different keywords?) for duplicates and use a better title than Had Enough of UI Error the next time you want to open an issue. Thank you.

This answers absolutely nothing. Since you know I'm not able to find whatever issues you're referring to, why don't you link me to them instead of just responding with something that doesn't help at all. I came to you cause like I already said I've been doing research on it.

[quinb96]

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.

You didn't, your issue is a duplicate of multiple closed ones. Please search (better, with different keywords?) for duplicates and use a better title than Had Enough of UI Error the next time you want to open an issue. Thank you.

Like can you suggest keywords or something or just continue to provide me information that doesn't answer anything I said?? Any kind of help YOU can provide me at all?

[opusforlife2]

Any kind of help YOU can provide me at all?

For any Github (or similar) project, always have a look at pinned issues before doing anything else. Depending on the platform, there may be pinned/stickied discussions/topics etc.

[quinb96]

Any kind of help YOU can provide me at all?

For any Github (or similar) project, always have a look at pinned issues before doing anything else. Depending on the platform, there may be pinned/stickied discussions/topics etc.

I already stated that I've done all maybe 3 times. Just read what I said. You guys keep telling me to search the closed issues foe a fix and one doesn't seem to even exist. And you guys refuse to link me to an issue that may solve my problem. There doesn't seem to be fix based on all the issues I read. I'm done with this though. There's no incentive to fix this issue. I'm just going to use LibreTube.

[opusforlife2]

I already stated that I've done all maybe 3 times.

Did you read the pinned issues? You haven't stated that anywhere.

[quinb96]

I already stated that I've done all maybe 3 times.

Did you read the pinned issues? You haven't stated that anywhere.

Yes and none of them are related to my problem. There's maybe 25+ people complaining about the same problem. Even Audric said this. And you guys are telling people do this and do that to fix the issue but we shouldn't have to do anything. It should just be working. I'm sorry but there's clearly a bug in that. I'm confused cause it sounds like Audric is aware that this an issue and still decided to tell me to just look at closed issues. I was already extremely frustrated from this app acting like this and Audric didn't make it any better responding the way he did about something that clearly plagues the app. When I've witness you guys actually try to assist other people in this. The title of the issue doesn't matter. I explained thoroughly what the issue is so mentioning the title was a bit petty.

[opusforlife2]

Ok cool, you've searched the pinned issues and haven't found your problem or its solution.

Next step is to search issues using the first line of the crash log. So in this case, you'd use something like android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException, which you can see in your posted crash log.

[quinb96]

Ok cool, you've searched the pinned issues and haven't found your problem or its solution.

Next step is to search issues using the first line of the crash log. So in this case, you'd use something like android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException, which you can see in your posted crash log.

I'm done. I'll leave you guys alone.