As you can see in my screenshot, this error happened when my friend opened my game ( so he’s done with downloading expansion files ) , but I’m not sure if it is right after the download or not ( maybe he downloaded files, closed game, re-opened it many times and this error occured ).
The zenphone series is running Intel Atom chips. These chips have an ARMv7 emulation mode that Corona SDK should work on in most cases, it’s not perfect. I would suggest filing a bug report to see if engineering can duplicate it. The hard part here is you are going to have to put together a project that has the issue and send it in with the bug report.
I’m really sorry that I can’t take a log. My friend checked it and just sent my a screenshot of it. It doesn’t happend frequently . Besides, I have never seen it on the Simulator.
I’m using libraries like: display, physic, graphics, audio, storyboard, timer, transition, json, math, Runtime, touch and accelerometer, v.v.v. I use Spine, too. But I took a look and saw it doesn’t use Widget.
Something somewhere is trying to use a widget.newProgressView() API. If you’re not using it, then a library has to be using it. No part of our core code calls that function. If you tether your device to your computer and use adb logcat as documented in the link I provided above, there will be a full stack trace. Perhaps you could get your friends phone and put it into developer mode and capture the message. You could also use the Android tools to setup a device emulator (not our simulator, but an emulator that is closer to the real device) and see if you get the crash there at which case you would have access to the device’s logs.
Without this, your only other choice is to look through all your other code and see if something is calling widget.newProgressView().
My IDE has ‘Search Whole Project’ function, I use this but see nothing calling newProgressView (don’t see this word anywhere) . I don’t use any 3rd lib calling widget.newProgressView().
I known how to use Android Debug ( I always use Dalvik Debug Monitor ). But as I said, this bug doesn’t happen frequently. I really can’t catch it now. That’s ok if you can be sure Corona’s core code doesn’t call that function.
Guess I need a little luck to meet this bug again and catch its log
I did a check with ‘grep newProgressView’ ( you made a mistake with newProgressview, right? ). I also went to sub directories myself and did that check again. I still couldn’t see anything calling it
I used my own tool to build my levels. It ouput xml files and I wrote a loader to read them. I used a xml library, but it only used string lib so I think it can’t be the problem.
If you show us the results of all four shell commands I listed, that might help. Otherwise you’ll have to wait until you get the error and include that from a device log.
Here what I got from CoronaLog. I got this report from google. That’s all I have for now
java.lang.RuntimeException: /Users/jenkins/slaveroot/workspace/Templates/label/android/subrepos/widget/widgetLibrary/widget\_progressView.lua:225: attempt to index field '\_view' (a nil value) stack traceback: [C]: ? /Users/jenkins/slaveroot/workspace/Templates/label/android/subrepos/widget/widgetLibrary/widget\_progressView.lua:225: in function 'finalize' /Users/jenkins/slaveroot/workspace/Templates/label/android/subrepos/widget/widgetLibrary/widget.lua:65: in function 'method' /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:529: in function 'remove' /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/android/ndk/shell.lua:183: in function 'removeAllUi' /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/android/ndk/shell.lua:211: in function 'func' /Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:241: in function \</Users/jenkins/slaveroot/workspace/Templates/label/android/platform/resources/init.lua:221\>