03-13-2012 05:39 PM - edited 03-13-2012 08:36 PM
I encounter a problem when trying to install an app. that has just been approved on AppWorld (using my sandbox account).
The procedure worked fine with the previous version of the app.
Here is what happens when I try to install the app.:
-select app. in AppWorld, and "Purchase": ok
-enter BB ID password for user authentication (the BB ID declared in the sandbox): ok
-select "Buy Now": the app. appears in the AppWorld "My App" (with the green circle next to it)
... then disappears silently. No error message. Nothing else. And the app. is not installed.
-So I have no clue to know if the problem is related to the sandbox account (again, it was working fine with the previous version)
-I don't know if it is related to the app. new version (but the app. has been approved, and all my usual forward tests were ok (install debug version, install signed version in dev. mode)
-and I don't even know if users who paid for the previous version can download/install the new version normaly !!
Any feedback on this issue will be highly appreciated.
03-13-2012 07:35 PM - edited 03-13-2012 08:39 PM
Here a quick update:
I just tried to download another app. "B" (previously installed with same sandbox account) and I had same error.
(the good news is that it seems that my app. "A" new version is not corrupted).
So I think the problem is linked to AppWorld and the use of sandbox accounts.
-Has something changed about sandbox accounts ?
-Is it a known pb with AppWorld ?
I may add that the apps. are not in Draft, but on sale.
Nevertheless I also tried to use the method described for "draft" app. (typing "tst" in AppWorld), but with same error result.
And I also tried to set back the app. to draft mode, then use the "tst" method to open it in AppWorld: same error
=> I really think something is wrong with AppWorld+sandbox account
Kinda lost here....
03-14-2012 08:23 AM
There is a bug in AppWorld that deals with the sandbox. RIM is aware of the issue and are trying to resolve it. If you want to purchase your own app, you have to remove yourself from your sandbox. It probably causes problems with in-app purchases as well that have the purchaser in the sandbox.
03-14-2012 07:36 PM
Hi jtegen, thanks for the answer.
I guess this is an issue from 2.0... it was working fine before.
Do you know where I could consult the bug resolution advancement ?
03-15-2012 09:00 AM
03-20-2012 12:40 PM
03-20-2012 02:58 PM
Refer to this post for details on the issue. It'll also be updated once the problem has been fixed.