cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Stiefel (JIRA)" <>
Subject [jira] [Commented] (CB-2302) NullPointerException at org.apache.cordova.AudioPlayer.destroy(
Date Tue, 20 Jan 2015 08:22:34 GMT


Philip Stiefel commented on CB-2302:

I'm facing the exact same problem. Is there a fix to get rid of that problem?
I'm starting a audio stream by pressing a button - when I press it again, another stream starts
again and the first one does not stop.
When I close the app, I crashes with the error message above.

- Android Studio 1.0.2 Build 135.1653844
- Android API Level 21 (Lollipop)
- Latest Cordova build fetched via "npm install cordova" - Version 4.2.0

I hope you can help me out and if you need additional information, please let me know.

> NullPointerException at org.apache.cordova.AudioPlayer.destroy(
> ------------------------------------------------------------------------------------
>                 Key: CB-2302
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 2.2.0
>            Reporter: r yoo
>            Assignee: Joe Bowser
> We got this crash report, looks like cordova is messing up when trying to kill the audio
player. Not sure which android version this is, sorry.
> java.lang.RuntimeException: Unable to destroy activity {our app}: java.lang.NullPointerException
> at
> at
> at$1200(
> at$H.handleMessage(
> at android.os.Handler.dispatchMessage(
> at android.os.Looper.loop(
> at
> at java.lang.reflect.Method.invokeNative(Native Method)
> at java.lang.reflect.Method.invoke(
> at$
> at
> at dalvik.system.NativeStart.main(Native Method)
> Caused by: java.lang.NullPointerException
> at org.apache.cordova.AudioPlayer.destroy(
> at org.apache.cordova.AudioHandler.onDestroy(
> at org.apache.cordova.api.PluginManager.onDestroy(
> at org.apache.cordova.CordovaWebView.handleDestroy(
> at org.apache.cordova.DroidGap.onDestroy(
> at our app.onDestroy(our app:144)
> at
> at
> at
> ... 11 more
> our onDestroy doesn't do anything special, just sets an internally used "isFocused" boolean
in the activity to false before handing off to super, so it can't be us right? First and only
time I've seen this, our app has been in the wild for months, been using 2.2 for a while.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message