Random "UI error" causes a crash

[ghost]

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

1. Open the app as normally
2. Start downloading videos & subtitles
3. Use the app as normally (watch other videos, search, look at the download progress)
4. At any given backswipe to go to the previous screen (especially from the downloads progress view), the app will crash, and give an "UI error"

Expected behavior

The app should have worked normally, no crashes, et cetera.

Actual behavior

The app will crash at any given time, especially if you look at the downloads view, and go back to the previous view by tapping back on the system nav bar.

Screenshots/Screen recordings

No response

Logs

Exception

• User Action: ui error
• Request: ACRA report
• Content Country: ZA
• Content Language: en-ZA
• App Language: en_ZA
• Service: none
• Version: 0.25.2
• OS: Linux samsung/a33xnsdxx/a33x:13/TP1A.220624.014/A336EDXU6CWF1:user/release-keys 13 - 33

Crash log

android.app.ForegroundServiceStartNotAllowedException: Service.startForeground() not allowed due to mAllowStartForeground false: service org.schabi.newpipe/us.shandian.giga.service.DownloadManagerService
	at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel(ForegroundServiceStartNotAllowedException.java:54)
	at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel(ForegroundServiceStartNotAllowedException.java:50)
	at android.os.Parcel.readParcelableInternal(Parcel.java:4787)
	at android.os.Parcel.readParcelable(Parcel.java:4755)
	at android.os.Parcel.createExceptionOrNull(Parcel.java:3018)
	at android.os.Parcel.createException(Parcel.java:3007)
	at android.os.Parcel.readException(Parcel.java:2990)
	at android.os.Parcel.readException(Parcel.java:2932)
	at android.app.IActivityManager$Stub$Proxy.setServiceForeground(IActivityManager.java:6991)
	at android.app.Service.startForeground(Service.java:743)
	at us.shandian.giga.service.DownloadManagerService.updateForegroundState(DownloadManagerService.java:336)
	at us.shandian.giga.service.DownloadManagerService.handleMessage(DownloadManagerService.java:268)
	at us.shandian.giga.service.DownloadManagerService.$r8$lambda$gVT-KbstFlv6SWFsotFx97l7BIY(DownloadManagerService.java:0)
	at us.shandian.giga.service.DownloadManagerService$$ExternalSyntheticLambda2.handleMessage(R8$$SyntheticClass:0)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loopOnce(Looper.java:226)
	at android.os.Looper.loop(Looper.java:313)
	at android.app.ActivityThread.main(ActivityThread.java:8757)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

---

Affected Android/Custom ROM version

Android 13, with OneUI 5.1

Affected device model

Samsung Galaxy A33 5G (SM-A336E)

Additional information

No response

[ZybanX]

I think android is preventing the service from starting in the foreground. This could be due to a restriction imposed by the Android system or by the app itself.

Edit: When leaving Newpipe, Samsung kills the app when not using to improve battery life. See the reference here

[ghost]

I think android is preventing the service from starting in the foreground. This could be due to a restriction imposed by the Android system or by the app itself.

Edit: When leaving Newpipe, Samsung kills the app when not using to improve battery life. See the reference here

Didn't think of the shitty OneUI app power management, but i'll definitely adjust the battery optimization settings for newpipe.
Though at some point (before this) I'd see a system pop-up telling me that the app isn't responding at random (I could be watching a video, or monitoring the downloads view and this would happen), then I knew if I were to swipe back, or tap back, the app will crash.

[ShareASmile]

It was due to harsh battery optimizations in Samsung OneUI Device care App updates, but cannot verify if it still happens on user's device as user has deleted his account. I am using Samsung device on Android13, OneUI 5.1, Device Care version 13.6.07.4 & battery saver always ON , Battery set to optimized for NewPipe and found no problems in past months.

Hence Closing. If anyone faces issue having similar logs containing "Service startForeground not allowed due to mAllowStartForeground false" Can open a new issue please.