-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Plugin crashes Android app #5
Comments
As mentioned in the fork, we have also the same issue with this Verified Plugin. |
@Lecramed what mention in which fork are you referring to? And is it also (only?) a problem on Android 6? Do you guys have any crash logs you can share perhaps? |
How can i create a crash log. My main target is IOS so i do not have much experience with android. |
@Lecramed |
Here is the log of the crash |
So according to the upstream repo it's possibly fixed by updating to the latest Android libraries. But when building with Telerik Platform you don't really have much control over that. Not sure why this suddenly breaks though. |
I have a bit more information regarding this error. And here is a logfile of adb logcat at the same time : I hope this will assist in debugging this problem. On a side note, I did test on older versions of android and the problem does not exist there with this version of the plugin. |
Hey guys, I've just updated this fork to the latest bits of the upstream repo so in case you Android repo's are up to date you should have the same behaviour as with that one. Can you please verify this on your end with version 6.0.0? Thanks! |
@EddyVerbruggen |
My app has been live with the new plugin for about 1 and a half months without any problems so far, as mentioned in this issue. The problem has been solved according to me. |
Everything was working just right until couple days back. Plugin calls like registerDevice and unregisterDevice are causing app to crash without being able to produce an exception in debug mode. (using the Visual Studio Telerik AppBuilder client). Is this a known issue? Has anyone encountered a similar problem lately? Using Android 6
The text was updated successfully, but these errors were encountered: