-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
App crashes when in background #9070
Comments
This comment was marked as spam.
This comment was marked as spam.
I don't understand what you're writing in your comment, but this appears to be a duplicate of #9053, which in return appears to be a duplicate of #9030, and eventually this crash was described in #8646 (comment). |
@tsiflimagas Sure? I'm no dev, but the STRs don't seem similar, despite the exception possibly being the same. |
There could be a problem by clicking the search history. Follows app crash. |
Tbh I had by doubts thinking it again, as I'm not a developer either. Let's wait for one I guess. |
I noticed the same since the last version. I haven't been using the app for several hours (at least 6h), before I get the error. Exception
Crash log
|
I can confirm what @Rominet13 said. The app doesn't even have to be focused for this to occur. Just having the app in the background (not manually swiping closed from switcher) is enough to trigger the error. Newpipe will take focus back from whatever the current app is to display a near identical error to everyone else. I'm not sure what I would have done to cause it given the app wasn't open. |
I've gotten a report about this from a user, too. The app can randomly crash while the user is busy using some other app. |
Ok, it always appears when disconnecting (and sometimes when connecting) bluetooth devices like a car or loud speaker (My watch is connected too but I don't think it changes anything.) |
Right. That's a known problem and has more to do with Android. Before version 0.24.0, you just got a blank player notification, since Newpipe was the last "media player" app used. Now it causes a crash. @Stypox This seems actionable now. Is there a way to prevent Newpipe being seen as a media app by the OS? It obviously has something to do with the changed player code, but we might be able to bypass the problem entirely. |
Can you all confirm that you haven't disabled the Newpipe player notification in your OS settings? I'm interested in knowing if your player notification is showing just fine and you still get this error. I'm trying to narrow this bug down and the lack of the player notification may be a cause, since that's what Android uses to determine if the app should be kept in memory or not. |
If by "Newpipe player notification", you mean the "Hide player when the media session has ended (the player allows you to resume a session from the expanded quick setting panel)", it is disabled. I have never changed it... I didn't know it exists^^. (All other notification are on by default for the app) |
I'm... not sure, actually, if that Android 11+ setting matters. What I'm asking specifically is that when you play a video in the main player, popup player, or the background player, does the player notification show in the notification shade? |
Yes the player is in the notification shade, and I use it. |
Alright, that's a dead end, then. Thanks for confirming! |
This comment was marked as off-topic.
This comment was marked as off-topic.
This looks like the same issue that I have started seeing over the past week or two with my NewPipe client. Reproduction steps for me were similar to already mentioned: Play a video in background, stop playback, then connect the phone to the car (or presumably any other Bluetooth device that causes autoplay). I was able to create a Tasker task to take over media events and saw the crashes go away which confirms it was definitely Bluetooth autoplay which triggered the bug. I've had this happen both with the player in the notification shade and after dismissing the player by hitting the "X" in the lower right. Pressing "Play" on a pair of headphones also seems to trigger the bug. |
I get this error on grapheneos Exception
Crash log
|
@esibun Could you confirm the bug for 0.24.1, please? |
Tried this earlier against 0.24.1 and was unable to reproduce. Might be fixed but should be able to say for sure this afternoon. |
I reproduced the issue last night in my car (Bluetooth connection) using
0.24.1 so it's not resolved. As someone earlier said, it has something to
do with Google play services so changes can happen at any time without us
knowing.
…On Wed, Nov 9, 2022, 12:39 PM esibun ***@***.***> wrote:
Tried this earlier against 0.24.1 and was unable to reproduce. Might be
fixed but should be able to say for sure this afternoon.
—
Reply to this email directly, view it on GitHub
<#9070 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFTL6G24RZQL73UYJGH7ATWHPOVJANCNFSM6AAAAAAQ5HFTOA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I've also been experiencing this issue about several times a day for the past two weeks. I am using the SponsorBlock fork, but the log is similar (and nearly identical to @kirkawolff's) For the log below, I only had NewPipe paused in the background while scrolling through another app. I was using Bluetooth ear buds, but I wasn't doing anything with them at that time. Furthermore, pressing play from them does not cause NewPipe to crash in my case, unlike what others have mentioned. I also don't have Google Play Services installed. Exception
Crash log
|
Checklist
Affected version
0.24.0
Steps to reproduce the bug
Use multitasking to go back to NewPipe app and can cause crash. Foreground running occured. There was a problem with search suggestions which caused by their multitasking action.
Expected behavior
The app worked fine without errors.
Actual behavior
Crashes with running in foreground service exception unable to start with correct time
android.app.ForegroundServiceDidNotStartInTimeException
as it appears it can't look up search suggestions.Screenshots/Screen recordings
See logs below.
Logs
Exception
Crash log
Affected Android/Custom ROM version
Android 12 [Global India ROM, realme UI 3.0]
Affected device model
realme 8 4G
Additional information
No response
The text was updated successfully, but these errors were encountered: