Closed gabaum10 closed 7 years ago
I'm using cordova 6.3.1 and cordova Android 5.2, building from the command line.
Just to be clear, the push notifications work correctly and everything initializes fine. It's just when the user force kills the app they get the "has stopped" popup. This doesn't happen when I do a build without te pushwoosh plugin.
Also, have you guys tested everything in a crosswalk environment? That's the only think that I can think of that might be causing conflicts. I'm using the Cordova Crosswalk Plugin.
I dropped the version of the pushwoosh plugin to 5.0.0 for comparison purposes, and it didn't throw the error. I guess I could just do a binary search through the versions until I find the one that broke it...
Ok, I narrowed it down to the release that introduced the bug.
It was something from release 6.2.6 to 6.3.0, specifically 914545fdb884e4dbc653080b2350204aa3b07ccd. However, those changes don't look like they would cause this. I do see the framework was updated from com.pushwoosh:pushwoosh:4.6.3 to com.pushwoosh:pushwoosh:4.10.1. Maybe that did it?
6.2.6 works correctly.
Hi,
Could you please provide us with a bit more details on your issue? Particularly, when exactly is this error message shown: right after a user force stops your app or when he relaunches it?
Also please provide us with your device console log with the moment when this alert is shown captured?
The error message in the title is the exact error message. Unfortunately, <App Name> has stopped.
. It happens immediately after the user force kills it. For example, open up the list of running apps and swipe it right to kill it. Or say Kill all, something like that.
Which logs do you want? The one from the chrome developer tools?
Hi,
It would be helpful to see the logs from the device itself, illustrating the crashes, specifically the stack trace
from adb logcat
. Thanks!
Weird, I just updated to the latest (6.4.2) and it's not happening anymore. Now, I did update cordova CLI to version 6.5.0 at some point since I opened this issue. That may have helped too. I was on like 6.2.x or maybe even lower.
I'm using version 6.4.1 and I don't see any mentions of this.
When the user force kills the app, a popup comes up and says "Unfortunately, App Name has stopped." I have narrowed it down through the process of elimination to be this plugin that's causing the error. I have no idea why that would be.
I have no way of debugging this because it's too late for the traditional debug tools. Has anyone else reported this?