There is crash protection in the pro level which I'm assuming you don't 
have.
Normally you can connect a cable and look at the logs to see what went 
wrong but that might not work well for iDevices without a Mac and due to 
recent changes from Apple might not work well for iDevices at all.

If you have a Mac you can also debug the project on xcode and see the 
output/exceptions 
https://www.codenameone.com/how-do-i---use-the-include-sources-feature-to-debug-the-native-code-on-iosandroid-etc.html

Finally you can try to isolate a standalone test case with no logic that 
still fails and file an issue. Since this is a recent regression it might 
relate to the Cordova support that the bluetooth code relies on. I know 
Steve made some changes to the JS library layer so maybe he has an idea.

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/7b84b792-147a-4e90-9212-415c6bc94888%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to