java.lang.NullPointerException: Attempt to invoke virtual method 'void [android.support.v4.media](http://android.support.v4.media).session.MediaSessionCompat.setQueue(java.util.List)' on a null object reference
at de.danoeh.antennapod.core.service.playback.PlaybackService.lambda$loadQueueForMediaSession$1([PlaybackService.java:350](http://PlaybackService.java:350))
at de.danoeh.antennapod.core.service.playback.PlaybackService.$r8$lambda$3kCEWuNcq1SHYOtaxSddkU4SmrY([PlaybackService.java:0](http://PlaybackService.java:0))
at de.danoeh.antennapod.core.service.playback.PlaybackService$$ExternalSyntheticLambda13.accept(R8$$SyntheticClass:0)
at io.reactivex.internal.observers.ConsumerSingleObserver.onSuccess([ConsumerSingleObserver.java:62](http://ConsumerSingleObserver.java:62))
at io.reactivex.internal.operators.single.SingleObserveOn$[ObserveOnSingleObserver.run](http://ObserveOnSingleObserver.run)([SingleObserveOn.java:81](http://SingleObserveOn.java:81))
at [io.reactivex.android](http://io.reactivex.android).schedulers.HandlerScheduler$[ScheduledRunnable.run](http://ScheduledRunnable.run)([HandlerScheduler.java:124](http://HandlerScheduler.java:124))
at android.os.Handler.handleCallback([Handler.java:751](http://Handler.java:751))
at android.os.Handler.dispatchMessage([Handler.java:95](http://Handler.java:95))
at android.os.Looper.loop([Looper.java:154](http://Looper.java:154))
at [android.app](http://android.app).ActivityThread.main([ActivityThread.java:6315](http://ActivityThread.java:6315))
at java.lang.reflect.Method.invoke(Native Method)
at [com.android](http://com.android).internal.os.ZygoteInit$[MethodAndArgsCaller.run](http://MethodAndArgsCaller.run)([ZygoteInit.java:872](http://ZygoteInit.java:872))
at [com.android](http://com.android).internal.os.ZygoteInit.main([ZygoteInit.java:762](http://ZygoteInit.java:762))
Pardon me if that was a naive question, but my phone is on Android 14. Is it logical that app developers would still test for Android 7 that was introduced in 2016?
Unfortunately, many phone manufacturers don’t update their (older) phones to newer Android versions. If you want to be sustainable, holding on to an older device is the best thing you can do.
That’s for the user. And as long as the app developers choose to support an Android version (which AntennaPod does), I personally think it’s fair to expect the app to work for that version. Actively test, I don’t know. But not dismiss reports (otherwise, the developers should just not support that version any-more).
I have no idea.
A few times when I do activity on another page, and return to AP, the previous page displayed is replaced with the large “A” of the app initial page displayed. I tap on the letter and the previous page is displayed. No issue with this. Just a very small inconvenience.
I certainly concur on the sustainability point. I’m just oscillating between shock and being pleasantly surprised that AntennaPod supports the use of an Android version that Google stopped supporting (and providing security updates for) years ago.
The StackTrace can be very helpful, yes. It seems the Discourse mangled it, but I hopefully managed to recreate it by removing all the inserted http links. If you ever wish to paste technical information like this again, please try clicking the </> symbol (or press Ctrl-e) for adding Preformatted text, which the editor will not try to be smart with.
I agree. It is a shame this report initially turned into a conversation about android versions.
A few months has passed and a couple of new AntennaPod releases were made, with quite some changes to the code. The PlaybackService.java file has seen changes, but the actual null referencing method appears very similar between the versions.
Does this still happen with 3.4.0? Could you give some additional context? Is it easy to reproduce or does this crash happen seemingly randomly? Could you describe what you did immediately before the crash, helping to understand the cause? Did it work better in versions older than 3.2.0, and would you know one where it never crashed at all?
It appears this exact same crash got reported again in this thread. The second report has a few more details (and an unmangled stack trace, thanks!):
Added detail:
NO UNUSUAL BEHAVIOR OTHER THAN COVER ART BEING REPLACED
WUTH GRAYED BOX WUTH PODCAST NAME
AFTER DEVICE IS AWAENED AFTER USING
SLEEP TIMER
FIR PLAYBACK.
The above answers some of my questions in my previous comment, but it would still be interesting to confirm whether this has been seen also with 3.4.0?
