@zhangxm I know this type of bug is caused by some kind of promise code error without a catch() function. But which file / which line causes it ? How can i find it in my code. I have a lot of promise function so there is hard to check.
This bug is from logcat on android btw.
On the Build Panel, try the following steps.
Debug
Encrypt JS
then you can address the specific line when the JS code causes errors.
does this mean that if i encrypt the code, there is no way to catch a ts crash on mobile ?
