Hmm, this looks very strange... Let me check how it works
with android:debuggable="true". I'll come back soon with results
of my investigation.
-- Dmitry Moskalchuk
--
You received this message because you are subscribed to the Google Groups "crystax-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crystax-ndk...@googlegroups.com.
To post to this group, send email to cryst...@googlegroups.com.
Visit this group at https://groups.google.com/group/crystax-ndk.
To view this discussion on the web visit https://groups.google.com/d/msgid/crystax-ndk/f680e30b-3946-4f87-86e1-b9dce29f54c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Jeff,
I just found this question was remaining unanswered, so I'm answering it now.
This crash was consequence of this bug: https://tracker.crystax.net/issues/1459. It is now fixed, and we've published new patch release 10.3.2, differing from 10.3.1 by this fix only. You can download it and use for release applications, app will not crash anymore even with android:debuggable set to "false".
-- Dmitry Moskalchuk
To view this discussion on the web visit https://groups.google.com/d/msgid/crystax-ndk/3340ad10-5e1d-156d-1159-976b372fccbc%40crystax.net.