Hello, this is my build.settings https://pastebin.com/P1a0xSeQ
None of the excluded files are used in the new game that we released when the app start to carsh, in fact we do not change anything in this build.settings for this release.
We made an exahustive test on every device that we have, but unfortunelly we cannot reproduce the crash 
Thanks!
Admob plugin was updated in late August so it shouldn’t be an issue.
You say you added a mini-game. Do you have ads around it? Try testing your mini-game, press “back” button, etc. It’s not much I can suggest at this point.
This is the same error right?
pid: 0, tid: 0 >>> com.blackbean.tinypuzzle <<< backtrace:
#00 pc 000000000001a518 /system/lib/libc.so (abort+63)
#01 pc 0000000000365883 /system/lib/libart.so (art::Runtime::Abort(char const*)+402)
#02 pc 0000000000427117 /system/lib/libart.so (android::base::LogMessage::~LogMessage()+454)
#03 pc 0000000000387ead /system/lib/libart.so (art:
:AssertNoPendingException() const+832)
#04 pc 00000000000efc41 /system/lib/libart.so (art::ClassLinker::FindClass(art::Thread*, char const*, art::Handle<art::mirror::ClassLoader>)+28)
#05 pc 000000000028017f /system/lib/libart.so (art::JNI::FindClass(_JNIEnv*, char const*)+1310)
#06 pc 0000000000031774 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/libcorona.so
#07 pc 00000000001068bc /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/libcorona.so
#08 pc 000000000000cc1c /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so
#09 pc 000000000000d01c /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so
#10 pc 000000000000c084 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so
#11 pc 000000000000c0e0 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so
#12 pc 000000000000c188 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so
#13 pc 000000000000ca6c /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so
#14 pc 000000000001ce30 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so
#15 pc 000000000000d068 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so
#16 pc 000000000000c374 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so
#17 pc 000000000000d1e0 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so
#18 pc 00000000000055b8 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/liblua.so (lua_pcall+88)
#19 pc 0000000000107070 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/libcorona.so
#20 pc 000000000009ade4 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/libcorona.so
#21 pc 0000000000141244 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/libcorona.so
#22 pc 000000000008d4f8 /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/lib/arm/libcorona.so
#23 pc 000000000001c07f /data/app/com.blackbean.tinypuzzle-6R7cUnSSB60sIOZmxRYBQg==/oat/arm/base.odex
Yes, it is. May I ask to use pastebin to share crashlogs? It is hard to read like this.
Sure Vlads, here are my top 4 crashes, as you can see we are experimenting a lot of crashes but all of them seems to be the same problem.
Are this all from same version 2018.3350?
Yes, all this crashes are from version 2018.3350
Regards
Hello!
This look much better! Here are symbolicated crashes. What happens here is following:
Update Display::Update(), which dispatches “enterFrame” event.
Then it executes the event and error during invocation or executing of the event.
Enter Frame can have many things in it, it’s a workhorse of things like transitions or timers, so error may happen like inside a timer or transition, trying to access deleted widget or display object or something.
So this error is caused by some Lua code, and should be reproducible. Also, it is weird, because usually Lua errors should not crash the app. Do you use some custom error handling?
Great we are closer… here are 3 questions:
1-We recently added this block of code trying to catch the error, but unfortunely we have no luck. We have not received any crash report from the app. Is there any chance that this error handler is hinding the cause of the error?
2-Is there any way to get the lua filename to find in wich screen is crashing?
3-Did you recommend that i try to remove every enterframe handler replacing it by transitions or this error can be caused by a timer to?
Thanks!
this is the error handler that we added:
local function handleUnexpectedError(event)
analyticsManager.logEvent( “Error”,
{
errorMessage=event.errorMessage,
stackTrace=event.stackTrace
}
)
end
Runtime:addEventListener(“unhandledError”, handleUnexpectedError)
There’s misunderstanding: I told that transitions and times utilize enterFrame within them. So the cause may be not your direct enterFrame handler, but some of timers.
Did you add that code after the crashes appear or before? I would suggest testing it first somehow. Errors in error handler is a nasty thing. Also, if your handler invoker network request it may cause problems.
Not on google console. It is hard to tell what is going on inside your Lua code.If you would have a repro for crash, you would see it in logcat output
Thanks for your help Vlads, we found an issue with a timer handler in the new mini game. I hope that this is the issue that was looking for. We already released a new version, so lets wait and see.
It would be great if someday we can get the stacktrace in play console just like we have in simulator, logcat, etc.
Best Regards