-
-
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
Crash when running two newpipe instances at the same time: java.lang.RuntimeException: Error receiving broadcast intent… #4653
Comments
I don't think we should put any effort into fixing this. Usually users do not have multiple NewPipes |
Also, this conflict doesn't happen between two release builds. At least one of them has to be a debug build. @Stypox But testers do have multiple Newpipes. And testing often involves comparing differences between them, especially when videos are playing. Testing would become absolute hell if I had to test one build, close it, then open the other and then test it, back and forth, back and forth. So to me this isn't low priority at all. Medium priority at least. :P |
Or developers would have to ensure they're uploading release builds. |
A debug build doesn't cause problems when used alongside a pre-0.20.0 debug build. So there is definitely something in the new version. My guess is the notification code, since that also seems to cause other problems as users have noted. |
This comment has been minimized.
This comment has been minimized.
When they test, they do. When they install a debug apk which fixes newpipe (right now), they do. |
I have a similar problem too. when running multiple debug builds and having their notification present. if you close one, then start playing on the other, the closed one appears again. I remember seeing in the code somewhere a hardcoded ID for broadcast (or something similar) towards the notifications. With multiple apps they would all them receive it. Edit:
|
All broadcasts should use package name instead of hardcoded strings |
Not to mention the related bugs: if you pause one NewPipe, the other one will resume. If you delete the notification from one NewPipe, the other one will delete notification too |
The actual reason is because package name isn't org.schabi.newpipe on debug builds. NewPipe/app/src/main/java/org/schabi/newpipe/player/MainPlayer.java Lines 66 to 85 in 1b47a1a
|
it fixes issues with forks or debug builds, e.g. when you open two newpipe apps (with debug or fork apps), close one notification, it closes all newpipe notifications fixes TeamNewPipe#4653
it fixes issues with forks or debug builds, e.g. when you open two newpipe apps (with debug or fork apps), close one notification, it closes all newpipe notifications fixes TeamNewPipe#4653
it fixes issues with forks or debug builds, e.g. when you open two newpipe apps (with debug or fork apps), close one notification, it closes all newpipe notifications fixes TeamNewPipe#4653
it fixes issues with forks or debug builds, e.g. when you open two newpipe apps (with debug or fork apps), close one notification, it closes all newpipe notifications fixes TeamNewPipe#4653
Checklist
Steps to reproduce the bug
Actual behaviour
Crash
Expected behavior
Everything works fine
Logs
Exception
Crash log
Device info
The text was updated successfully, but these errors were encountered: