BlackBerry® World™ Development

[thubalek]

Hello, 

I just noticed that all my apps that have implemented In App Purchases return error code 3 with message "There is no getExistingPurchases Local Cache".

Is it related to today's upgrade of AppWorld and will it be fixed? Or it is error in my implementation of In App Purchases.

Thanks for any help

Tom

[gbeukeboom]

Which device and OS are you noticing this on? How was the application installed (side-loaded, download via sandbox account etec)?

[thubalek]

It regards Dev Alpha A with latest available OS 10.9.9.339, AppWorld v. 4.2.1.87.

It is my app and it was freshly downloaded from AppWorld. 

[gbeukeboom]

2320 is the latest build, it may be worth updating.

One thing to check, does your BlackBerry ID appear in your list of sandbox users in your vendor portal?

[thubalek]

Software Update on my Dev Alpha says that I have latest software. Will it be pushed later today?

Regarding sandbox: I have no idea I'm not familiar with this functionality. I'll look at it.

[gbeukeboom]

That OS was released a while ago, but you may have it. Could you check Settings > About > OS > OS Version? 339 may be the release.

[thubalek]

I just checked it and it says: Is this OK?

[gbeukeboom]

It looks very odd, the OS should not have a '9' in the second set. Please check the screen mentioned in my last message and let me know what it says.

Please also confirm if your BBID appears in the list of sandbox accounts.

[thubalek]

Device is updated OTA so I have no idea why there is 9 in version number.

Regarding Sandbox: there was nobody so I just added myself. 

Then I removed app and installed it freshly from AppWorld. 

Still the same error message.

You can try it by yourself. App is here: http://appworld.blackberry.com/webstore/content/18993522/ 

[gbeukeboom]

You don't need to be in sandbox mode, I was just asking to understand the environment.

I downloaded the app, but where does it check for existing purchases?

I also noticed that any error messages received to the app (user cancelling a purchase) are displayed in plain text as a toast message which is not a great user experience. It may be a good idea to provide more user-friendly messages: ex "User cancelled transaction" rather than the current "Payment System Fail [system error message details]"