11-21-2012 08:44 PM
Looking for some advice, I have uploaded an App, all good.
My second App (based on Gesture Sample) works for me locally, but the versions I have submitted for approval keeps getting denied due to "After Installing on Playbook, when opening the App, it closes by itself, App could not load"
I need to know how to debug this, Can I run the ProgName-1_0_0_1.bar file to test? Should I look at the code, how I upload, or Bar-Descriptor file? Maybe the assets?
Its tough because I try fixes, but have to wait days to be denied.
Any help appreciated, Thanks.
Solved! Go to Solution.
11-22-2012 08:33 PM
Thanks, Install works. Running the device-release works. Running device-build works. I must be uploading to appworld wrong. I'll wait another couple days to see if my latest try gets "DENIED" again.
11-23-2012 02:00 AM
I have a similar issue. I have an app that works fine on Playbook and Dev Alpha. Even tested it with my friends. Yet it got denied on AppWorld because 'the application didn't appear properly on the device. The application page seem larger than the device screen, the menus on the bottom was overlapping and the information on the page not been display fully'.
I tried to email back and ask for screenshots but received no reply.
So basically just looking at rewriting the app to Cascades.
11-23-2012 07:13 PM
If I install the signed app on my Dev Alpha (or Playbook), how could it be any different to AppWorld installing it on their device? It wouldn't be.
I think their testing device is borked.
11-23-2012 07:14 PM
i not had these experiences - i have a thought however, maybe it's to do with permissions and folder/file access? these will be the most obviously different aspects between a devuser and a normally downloaded and installed app
11-23-2012 07:19 PM
They aren't installed as devuser.
I test the signed release build on my devices. The same way that RIM would be testing them.
All the permissions are set (but only shared files is required). Nothing that would affect graphics anyway.