On IOS, if you get unlucky enough, there can be crashes that can't be trapped and logged with any codename1 mechanism. Of course, these things aren't supposed to happen, but I've encountered this class of bug multiple times, and several of these are still unfixed. When these fast/hard crashes occur, your only tools are (a) to use apple dev tools to diagnose. (b) to binary search to narrow down the cause to simple enough case to file as a bug.
Before you resort to such desperate measures, be sure you've really locked down all the catchable exceptions; the top level of ALL threads has to have a catch-all clause, and there are a lot of opportunities to create little threads that "shouldn't" need error catchers. -- 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/188b652c-acc1-4af8-b270-610afbe144bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
