01-24-2013 04:05 AM - edited 01-24-2013 04:09 AM
I am getting this error too.
Revenues dropped from a steady daily stream to 0 all of a sudden. Last purchase was with the following time stamp: 21-Jan-2013 12:58:04 AM

Decided to check it out. App works fine in Sandbox mode both on PlayBook and BB10 Dev Alpha.

Turned off both my Sandbox users. Downloaded the app from App World on PlayBook as any normal user would. Tried purchase.
The PlayBook displays a dialog box that says:
Error
The item you selected cannot be found.

I also get a PaymentErrorEvent on my PlayBook with the following text:
The digital good was not found. {30240}
I double checked digital good ID and SKU and they should be fine. I pass both to the purchase call. Digital good is Up For Sale on vendor portal.
This is a serious issue. I don't know how to resolve it. Can you help?
01-24-2013 11:49 AM
Hi! It's been a while, but were you able to solve this? I got this error for two specific products, and have no clue, since we have changed nothing on BlackBerry store side.
01-24-2013 04:15 PM
I have engaged the App World development team that is investigating this issue now. I will keep this thread posted with details.
01-24-2013 06:03 PM
Update: There has been an issue identified with the lates BlackBerry World update which has caused this problem for any users trying to use IAP with either credit card or PayPal set to their default method of payment.
A hotfix is being worked on with urgent priority and will be implemented as soon as complete and we have a window.
Until fixed the workaround would be to have the user switch their default payment method to carrier billing if the option is available to them.
01-24-2013 06:11 PM
Thanks for the update. Ballpark ETA?
App World QA might want to consider adding IAP to their test suite for future updates.
01-24-2013 06:14 PM
01-24-2013 06:37 PM
01-24-2013 06:42 PM
01-24-2013 08:02 PM
Thank you for replying. If you have any updated info, please let us know. Cheers!
01-28-2013 10:59 PM - edited 01-28-2013 10:59 PM
Folks, I just heard that the fix has been put in place and validated by our internal dev teams.
Please let me know if the problem is now resolved for your applications.