11-29-2012 10:08 AM
12-21-2012 06:58 AM
I followed the procedure with my DevAlpha and enter my App ID which is in Draft mode, and getting message "There was a problem loading this Page, due to a network error".
I got no network error, i can download other normal apps from AppWorld.
Is this procedure still working?
12-21-2012 07:56 AM
This seems to be broken at the moment. Dev is aware and an internal bug is logged.
12-21-2012 09:46 AM - edited 12-21-2012 09:48 AM
Now i got download page, but getting network error when i press Download button.
01-01-2013 07:26 PM
I'm getting the network error issue as well. I have an app uploaded in draft mode and cannot download to the Dev Alpha.
DM
mzex wrote:Now i got download page, but getting network error when i press Download button.
01-06-2013 05:14 AM
01-06-2013 08:53 AM
We are hoping to get some official answer from RIM. Developing apps which have in app payments or invite to download via BBM is very complicated if we dont have ability to do proper testing via draft mode in AppWorld.
01-07-2013 07:33 AM
Still working on a way to test in app payments, for now local mode will get you 95% of the way there.
BBM invites wouldn't really benefit from Draft mode though.
01-07-2013 08:09 AM
I cant test BBM invite to download, because, if app is not on AppWorld, user which get invitation to download, will get disabled invitation. Also, i have complex logic of in app payments, and i cant rely on local mode, because, i need to check previos purchases, and that cannot be done in local mode. Because of all this stuff, app which i was targeting to be B4BB, and eligible for 10K commitment maybe will not pass testing B4BB on time, because i need to clear bugs in it, regarding in app payments section.
01-07-2013 08:13 AM
For BBM it's still not overly helpful, even if the app is in DRAFT mode users won't be able to see the app directly, you need to enter the app SKU or content ID to download.
Past purchases can be checked in local mode if the purchases were made during the same session (without closing the app). The only other option at this point would be to do full live testing, but the iterations between cycles would be very long. If using a development language supported on PlayBook you could also use that to test for now.