I agree that running under a debugger on the device is not a complete solution. In particular, I wish for a permanent monitor on the deployed app to catch rare cases.
The problem in codename1 is that even if you identify a likely problem at runtime, there is no way to extract information about it. Which threads are blocked, waiting for which monitors, with what stack trace, for example. The standard java component ThreadInfo, or any subset of its functionality, would be very useful. -- 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/505afba8-357c-4b55-8742-66b409c32989%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
