09-15-2011 10:07 PM - edited 09-15-2011 10:37 PM
I am having the same problem as well with a Tapatalk forum reader app that I purchased. Tried the ALT + RST with no luck. First and last app I will ever buy from app world. As mentioned by others, the app no longer shows up in the installed or uninstalled apps. I HATE this blackberry. I want my iPhone back!
09-16-2011 02:05 AM
09-16-2011 02:00 PM
Ditto with having the same purchase service error # 30220. Tried that ALT + RST thing with no luck, tried re-installing App World with no luck. Updated my OS with no luck. Dreading that my next step is a full wipe and it still may not help.
Anyone have any thoughts on how to get this fixed or escalate it to RIM?
09-16-2011 05:23 PM
Sigh, I'd thought of that too. Whenever I try and purchase my app through my PC I'll click on the link to repurchase and then get an "HTTP 500 Internal Server Error" page. Any other thoughts anyone or know how I can escalate this to RIM?
09-16-2011 08:02 PM
09-16-2011 09:43 PM
Still no go - using IE I get the server error page and get no where in app world when attempting to purchase. Can't even see it as a re-install.
With app world on my phone I still just get the purchase service error 30220 whenever attempting to re-install my app. Soooo frustrating - dreading a wipe which is all my provider can suggest at this point too.
And can't seem to get anywhere with finding support from RIM - no records seem to exist for this error in any documentation or knowledge base.
09-17-2011 04:23 PM
Update: tired doing a full wipe on my phone and was still getting the 30220 error when trying to re-install my app. Finally called RIM to start some incident based support and got escalated with this error up a few levels of support folks. Ultimately it boiled down to an error they don't have a resolution for - so now RIM's developers have my error logs and screen shots and intend to work on including a resolution in the next version of App World. Strangely, I feel better knowing it wasn't me going crazy! :-)
09-17-2011 04:32 PM
09-18-2011 03:56 PM
Going through the web browser corrected it for me. Glad to hear from the person above who took the time to escalate this within RIM support.