Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Payment Service

Reply
New Developer
Posts: 48
Registered: ‎06-26-2011
My Device: Blackberry Playbook
My Carrier: none

Re: in-app purchase error code 30242

I don't know which version of app You are using.

If You could check this in Security -> application permission?

Version accessible for all is 1.0.69.0

 

I've put new file and it's in draft mode (v 1.0.82.0).

Both version are installed through app world.

Version 1.0.69.0 doesn't have functionality saying that there are no purchases. I've implemented it in 1.0.82.0.

When I press Buy button in 1.0.69.0 I got system error saying that Item couldn't be found.

 

When I run 1.0.82.0 (in sandbox mode) I have notifications from payment system enabled and there is  Error with ID 3 and description "The parent application could not be located within the reconcile cache".

When I want to buy 1.0.82.0 version I got error 30242.

 

I haven't got another device I can test with :/

Retired
Posts: 2,559
Registered: ‎10-16-2009
My Device: BlackBerry Z10
My Carrier: Bell

Re: in-app purchase error code 30242

App World shows it as 1.0.7, once installed I see it as 1.0.82.0 in Settings > Security > Application Permissions

Garett
@garettBeuk
--
Goodbye everybody!
New Developer
Posts: 48
Registered: ‎06-26-2011
My Device: Blackberry Playbook
My Carrier: none

Re: in-app purchase error code 30242

It's strange, because this version isn't approved. It just there as a draft.

Have You got access to the sandbox mode?

Retired
Posts: 2,559
Registered: ‎10-16-2009
My Device: BlackBerry Z10
My Carrier: Bell

Re: in-app purchase error code 30242

I've just installed the app normally through App World. Let me check my status.

 

At the same time could you try 1.0.82.0 and see if the same problem exists?

Garett
@garettBeuk
--
Goodbye everybody!
New Developer
Posts: 48
Registered: ‎06-26-2011
My Device: Blackberry Playbook
My Carrier: none

Re: in-app purchase error code 30242

It still doesn't work. I'd like to change license to paid.

Can existing users get refund for bought and broken digital goods?

Retired
Posts: 2,559
Registered: ‎10-16-2009
My Device: BlackBerry Z10
My Carrier: Bell

Re: in-app purchase error code 30242

Hi luko,

 

What still doesn't work?

 

You can request that your application be switched to paid by submitting a request to App World, however there are a few issues:

1) You cannot notify existing users of the free app proactively

2) Each paid user would need to request a refund which is a non-trivial procedure

Garett
@garettBeuk
--
Goodbye everybody!
New Developer
Posts: 48
Registered: ‎06-26-2011
My Device: Blackberry Playbook
My Carrier: none

Re: in-app purchase error code 30242

There is still 30242 error when user wants to purchase full version of app. Because of that I have many unsatisfied users and I didn't sell a single application for three weeks.

 

 

Retired
Posts: 2,559
Registered: ‎10-16-2009
My Device: BlackBerry Z10
My Carrier: Bell

Re: in-app purchase error code 30242

Yes, that bug has not been resolvd yet.

Garett
@garettBeuk
--
Goodbye everybody!
New Developer
Posts: 48
Registered: ‎06-26-2011
My Device: Blackberry Playbook
My Carrier: none

Re: in-app purchase error code 30242

[ Edited ]

I've lost a lot of time for this problem. It's very frustrating.

 

Can You please tell me how the procedure of refunds looks like?

 

 

Thank You very much for Your help.

Retired
Posts: 2,559
Registered: ‎10-16-2009
My Device: BlackBerry Z10
My Carrier: Bell

Re: in-app purchase error code 30242

I definitely sympathize with you on this issue, and I will keep you updated on the resolution as more information becomes available.

 

Customers can generally request a refund through standard support routes (opening a ticket with RIM), but in this case I am working with teams to find the best route forward to keep the process as easy as possible for users. I will post back today with more info.

Garett
@garettBeuk
--
Goodbye everybody!