You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2019. It is now read-only.
Experiencing a problem like #120. We are using the vkeepe Cordova plugin, but the problem seems so similar to #120 that I thought it would be most appropriate here (apologies if I'm wrong).
It crashes when it gets to the last line and we get this error:
2015-09-17 12:17:40.695 Skurt Dev[2008:387176] UXCam: Crash handler closing session. Caught exception: -[NSTaggedPointerString getCharacters:range:]: Range {0, 7} out of bounds; string length 6.
libc++abi.dylib: terminate_handler unexpectedly threw an exception
Unfortunately, we have another library that swallows the error, so I don't get the full stacktrace.
This happens on our iOS 9 device, but not our iOS 8 device. Is it possible that there is another localization bug like the one that caused #120? Thanks in advance for your help.
The text was updated successfully, but these errors were encountered:
Just to confirm, does this still happen with the latest (5.2.0) release? Can you temporarily remove the other library that swallows the error, so that we could get a full stack trace?
We have to focus on some other issues for the moment, but as soon as I have the chance to update and try it out, I'll update you. Thanks for checking in!
Experiencing a problem like #120. We are using the vkeepe Cordova plugin, but the problem seems so similar to #120 that I thought it would be most appropriate here (apologies if I'm wrong).
Our app runs this native code from the plugin:
It crashes when it gets to the last line and we get this error:
Unfortunately, we have another library that swallows the error, so I don't get the full stacktrace.
This happens on our iOS 9 device, but not our iOS 8 device. Is it possible that there is another localization bug like the one that caused #120? Thanks in advance for your help.
The text was updated successfully, but these errors were encountered: