I had a rejection from Amazon that the app force closes after tapping play button. Unfortunately I do not have Incredible. If you have Incredible, I’d really appreciate if you can test it for me. I promise it wouldn’t take more than 10 mins. Let me know. Thanks in advance. [import]uid: 19297 topic_id: 9853 reply_id: 309853[/import]
I have an Incredible and would be willing to test it for you.
My e-mail is skalistican@yahoo.com
I work the night shift so if you have it to me before I leave for work 10:00 p.m. (eastern time). I could let you know how it ran in the a.m.
Let me know [import]uid: 39088 topic_id: 9853 reply_id: 36097[/import]
Many thanks. I am sending you the download link shortly. [import]uid: 19297 topic_id: 9853 reply_id: 36101[/import]
Your Welcome
Got the link I will let you know how it runs when I get home. [import]uid: 39088 topic_id: 9853 reply_id: 36162[/import]
I tested your app last night and it ran on my incredible. No force close at all, not even once. The game did kind of run slow though. I was wondering what you set your fps to in your config.lua file? If you set it to 60 then changing it to 30 will greatly improve performance. At least it has for me on the app I’m working on. [import]uid: 39088 topic_id: 9853 reply_id: 36250[/import]
Wonderful! I noticed some slowness on some android devices, but on some (including iPhone 4) it runs very fast. I’ll try with 30fps. Thanksalotfor your feedback. [import]uid: 19297 topic_id: 9853 reply_id: 36259[/import]
your welcome, anytime [import]uid: 39088 topic_id: 9853 reply_id: 36363[/import]
Amazon came back with a little more information this time. Apparently it closes when they apply their DRM code on top of my apk file. Here is what I got from them:
“Your application attempts to call an Android Activity lifecycle method on a background thread. Amazon DRM does not allow developers to invoke Android Activity lifecycle methods on background thread. For more information on processes and threads, please visit: http://developer.android.com/guide/topics/fundamentals/processes-and-threads.html Additionally, the Android UI toolkit is not thread-safe. So, you must not manipulate your UI from a worker thread ? you must do all manipulation to your user interface from the UI thread. There are two rules to Android’s single thread model: * Do not block the UI thread * Do not access the Android UI toolkit from outside the UI thread”
After a few emails back and forth, it seems the application force closes when I call Director’s “changeScene” function. Only happens when Amazon tries to bundle their DRM code. The last email I got was “Your application attempts to call an Android Activity lifecycle method on a background thread” which causes force close.
Posted this in the Director’s fourm, also reported to Ansca. Not sure how much I can figure out looking at Corona code. [import]uid: 19297 topic_id: 9853 reply_id: 36395[/import]
That sucks man, all I know is it works on my Incredible. Did they send you a copy of your game with thier DRM code applied? I could test that for you or maybe some one from the Ansca team can look at it and see whats going on.
I have not tried to publish an app yet. Let alone to Amazon. But I know now that I might have to tweak my code if I did want to publish to Amazon.
Maybe its the UI class.
or Director [import]uid: 39088 topic_id: 9853 reply_id: 36435[/import]
Yea, really sucks. Awaiting response from Ansca. It could be the UI class as well that button because right out of UI class.
I’ll see if they can give me DRM wrapped code. [import]uid: 19297 topic_id: 9853 reply_id: 36454[/import]