No idea where to start with this stack trace crash

Solar2D Android
#1

This probably has to do with a user tapping the back button which would normally move back a screen or exit the app.  Anybody run across this and can offer some clues?  I don’t have any further info on this as it occurred in the field on Android 7.0.  Corona SDK 2017.3068

at android.app.FragmentManagerImpl.checkStateLoss (FragmentManager.java:1438)

at android.app.FragmentManagerImpl.popBackStackImmediate (FragmentManager.java:577)

at android.app.Activity.onBackPressed (Activity.java:2880)

at android.app.Activity.onKeyUp (Activity.java:2854)

at com.ansca.corona.CoronaActivity.onKeyUp (CoronaActivity.java:3460)

at android.view.KeyEvent.dispatch (KeyEvent.java:3346)

at android.app.Activity.dispatchKeyEvent (Activity.java:3155)

at com.ansca.corona.input.RaiseKeyEventTask$1.run (RaiseKeyEventTask.java:90)

at android.os.Handler.handleCallback (Handler.java:751)

at android.os.Handler.dispatchMessage (Handler.java:95)

at android.os.Looper.loop (Looper.java:154)

at android.app.ActivityThread.main (ActivityThread.java:6688)

at java.lang.reflect.Method.invoke (Native Method)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1468)

at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1358)

#2

Is there more to the error? 

What are you doing when the error triggers?

Rob

#3

Actually there was this at the top which I failed to paste:
java.lang.IllegalStateException :

in com.ansca.corona.CoronaActivity.onKeyUp

I have no idea what the user was doing at the time.  I’m only guessing from names in the call stack that it was a back button.  And I have no idea about the app state.   Does the stack trace give your team a clue about it?

Thanks, Jim

#4

I’m asking engineering about it.

#5

Can you create a demo project (main.lua, build.settings, config.lua and any needed assets) that at a minimum has your key event handling code in it and file a bug report.

We also want as much information as you can provide us, like the devices and OSs you’re seeing for this. If you can produce more log information that would be helpful too.  Once you have the demo project, put it in a .zip file use the “Report a bug” link at the top of the page.

Thanks

Rob

#6

That’s quite a bit of work to setup.  If we see this occur in the wild again we’ll look into doing that.  For now, we are going to just sit on it.  For log information, how would you suggest we capture/produce such a log in a published app? 

Thank you,

Jim

#7

Is there more to the error? 

What are you doing when the error triggers?

Rob

#8

Actually there was this at the top which I failed to paste:
java.lang.IllegalStateException :

in com.ansca.corona.CoronaActivity.onKeyUp

I have no idea what the user was doing at the time.  I’m only guessing from names in the call stack that it was a back button.  And I have no idea about the app state.   Does the stack trace give your team a clue about it?

Thanks, Jim

#9

I’m asking engineering about it.

#10

Can you create a demo project (main.lua, build.settings, config.lua and any needed assets) that at a minimum has your key event handling code in it and file a bug report.

We also want as much information as you can provide us, like the devices and OSs you’re seeing for this. If you can produce more log information that would be helpful too.  Once you have the demo project, put it in a .zip file use the “Report a bug” link at the top of the page.

Thanks

Rob

#11

That’s quite a bit of work to setup.  If we see this occur in the wild again we’ll look into doing that.  For now, we are going to just sit on it.  For log information, how would you suggest we capture/produce such a log in a published app? 

Thank you,

Jim