In app failing in store HELP!

Solar2D Monetization (in-app purchases, ads, etc.)
#1

Well what was supposed to be a fun day has been, well…less than stellar.

My inapp worked fine in development, all purchases, restores etc. The Inapp passed the apple review process…I can see the successful buys in test by Apple.

My app was released today…

In the store, it is not working…it appears as though now the customer is being charged for the inapp but I am not getting the callback or something along that line. I have turned off debugging when I submitted the app so my console output is limited…

Any suggestions on how to figure out what is going on?

I have written Apple.

I assume because the transaction went through the issue must be in my code?

Is it possible the inapp release lags the app release? Do I need to just wait?

All in-apps are cleared for sale…

No pending contracts…

Sigh.

Any help is greatly appreciated…

Rick

#2

Hey, Rick @afunnydevelopment, did you submit your IAP items and got them approved?  Check the iTunes and make sure that your IAP items are live.

Naomi

#3

Hi Naomi,

Thanks for checking in…

Yes, I submitted the IAPs when the app itself was submitted. All IAPs are approved and cleared for sale…are there other things I should be looking at???

thanks,

Rick

#4

In apps tend to take several hours to make it to the app store. It may be a delay. Did you include a restore option?

#5

Hi JonPM,

Okay that is good to know…yes, my app has a restore option…

If it is a waiting process it is a little lame that everything is marked good to go but in reality it isn’t. If this in fact is the case, now I know.

Thanks for the info.

-Rick

#6

Yeah hopefully that is the case, we’ll see. As a tip, when I begin working on an update that includes new inapps I will immediately submit the inapp well before the binary

#7

Guys can someone ease my mind:

If you look at your iTunes Connect -> manage in app purcahses is your state set to “ready for sale” or “approved” for each in-app?

Mine is set to “approved” and the cleared for sale set to “yes”. I am thinking it should be “ready for sale”???

What should it be? I think this is my problem.

#8

My IAP items for live apps show “Approved” and “Yes” for Cleared for Sale in iTC.

You mentioned IAP worked while you were testing in Sandbox – so I don’t think it’s the code.  Are you testing the live app with your Apple account?  If so, I wonder if you’ve signed out of your test user account, signed back in with your Apple user account with your credit card linked to it…?

Naomi

#9

Thanks Naomi,

I am using my real account (not a sandbox test account) when it fails. This account works fine for other purchases. I reloaded my development code to retry again and the sandbox works 100% fine with my test account. So I am quite perplexed…

Any tips on how to debug the released code? I have the xcode console available but my printf’s are turned off for the release build.

thanks again.

#10

I’m not sure.  You can try generating a release build with print statements?  That is, if you do use print statements for debugging.  (I solely rely on print statements to debug mine.)  You should be able to install the release build via Xcode and test it out.  It will send you to the sandbox for IAP, though – at least that’s how my release build installed directly on to my device usually behaves.

Also, do you have a flag that triggers different things between dev build and release build?  Can a flag causes your release build not to work the way it is intended to work while it doesn’t cause any issues with dev build?

Naomi

#11

Thanks for the time Naomi…

I have tried a couple things:

I built an adhoc version with the distribution certs (release) and inapp works…

I built a development version with development certs and inapp works…

I tried both of the above with and without console output and they work…

I reloaded the app store release version…it fails…

I do not know how to install a release build via Xcode…I would assume an ad hoc build with the distribution cert would be equivalent…maybe not?

Anyway thanks for your help…

Is the contact form via iTunes Connect the only way to get help?

-Rick

#12

Rick, you can load a distribution build (release build) directly to your device via Xcode, much the same way you do with adhoc build.  You may want to consider generating a new release build (using the same version number as the one already deployed to app store) with some print statements to figure out where IAP fails (if it does fail.)  

About contacting Apple, iTC contact form is probably the best bet.

Naomi

#13

Wait??? Are you saying build a release version with the same version for the store itself (load it on the store) or for a xcode load…

Sorry to keep picking your brain…I appreciate the help.

#14

I think for this to work, you need your device registered for adhoc build (i.e., provisioning profile loaded to the registered device), but yeah, I am able to load release build onto my device directly via Xcode.  I always do this to make sure the final build is not broken in anyway before I upload the zip file to iTC.

Naomi 

#15

After much pain I think I have figured out my problem…sigh

I do receipt validation as part of in-app…it was pointing to the sandbox receipt validation server versus the production one when building release code.

thanks for all the help…

#16

Glad to hear you were able to find the problem and solving it.

Naomi

#17

Hey, Rick @afunnydevelopment, did you submit your IAP items and got them approved?  Check the iTunes and make sure that your IAP items are live.

Naomi

#18

Hi Naomi,

Thanks for checking in…

Yes, I submitted the IAPs when the app itself was submitted. All IAPs are approved and cleared for sale…are there other things I should be looking at???

thanks,

Rick

#19

In apps tend to take several hours to make it to the app store. It may be a delay. Did you include a restore option?

#20

Hi JonPM,

Okay that is good to know…yes, my app has a restore option…

If it is a waiting process it is a little lame that everything is marked good to go but in reality it isn’t. If this in fact is the case, now I know.

Thanks for the info.

-Rick