iOS app crashes occasionally

  • 1
  • Problem
  • Updated 6 years ago
I have a live iOS app. It crashes alot for a fair share of my users, but not for many others. It seems to be limited to iOS 8.x, but I'm not certain.

I finally got my hands on a crash report, but I can't really interpret it to determine if this is a problem I can fix in my app, or if it's a problem with PG, PGB or a plugin.

App ID: 948817
Crash report: http://pastebin.com/kPjhKjay

Any assistance with this issue would be greatly appreciated!
Photo of Statens vegvesen Vegdirektoratet

Statens vegvesen Vegdirektoratet

  • 29 Posts
  • 0 Reply Likes
  • confused

Posted 6 years ago

  • 1
Photo of Yi Ming Kuan

Yi Ming Kuan

  • 1840 Posts
  • 78 Reply Likes
Seems like the error was caused by the LocalNotification plugin.

This plugin was contributed by a member of the PhoneGap community and isn't a first party plugin by PhoneGap. You can file an issue on the Github repo here and wait for the plugin maintainer to respond to it.

-yiming
Photo of Statens vegvesen Vegdirektoratet

Statens vegvesen Vegdirektoratet

  • 29 Posts
  • 0 Reply Likes
Thank you for a very helpful response. May I ask how you could determine from that crash log that the LocalNotification plugin is the cause for this crash? I was very puzzled by most of the contents of that crash report..
Photo of Yi Ming Kuan

Yi Ming Kuan

  • 1840 Posts
  • 78 Reply Likes
From the error log, the crash appears to be triggered when executing the cancelLocalNotification  function. This function is called in the LocalNotification plugin.

-yiming
Photo of Statens vegvesen Vegdirektoratet

Statens vegvesen Vegdirektoratet

  • 29 Posts
  • 0 Reply Likes
After browsing the LocalNotification plugin github issues I found an interesting comment in an issue concerning the cancelAll() function.

https://github.com/katzer/cordova-plu...

I will update the plugin in my app, but also implement the fix mentioned in the comment on github. With the insanely long approval times for iOS I'd rather go all-in right away to increase my chances of actually fixing this issue.
(As it took me a while to encounter the issue, even after several users reported it, I can't rely on testing the app myself before releasing it. This is obviously not how I usually test stuff... :))