How do I get Application Loader to accept a Corona build?

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

Pretty much in the same boat as horacebury; I’m trying to setup IAP for the first time and I get the message that I can’t connect to the iTunes store.

In horacebury’s thread, the suggestion seemed to be that I have to upload a build of the game and then reject it. However, Application Loader does not accept my build (the file is greyed out in the “Choose…” menu).

So my theory is this:

  1. Create a new provisioning profile for the game that is live (not dev)

  2. Upload a build with that certificate

  3. Cancel it immediately

  4. Hope and pray that IAP is unlocked later?

Any tips on this one?

#2

Well, answering part of my own question: 1-3 must be done. I wonder about #4 though - can we test using developer versions?

#3

This probably isn’t a recommended practice, but I tested my IAP’s first on Android, using live code.   I created the IAP, made the product free, uploaded the new version that uses IAP, and tested with a live Google Play account (different than the developer account).    It only takes 90 minutes for a new app to go live on Google Play, so the 2 or 3 revs I had to go through to fix issues wasn’t that big of a deal.   

I had paltry download numbers, so I wasn’t worried about potentially upsetting a large user base.   

Anyway, once I debugged all the issues with my use of the store API, I did the same for iOS.   Fortunately, the IAP interface worked the first time, which I was fairly confident it would since it worked on Android.   

#4

That is a really interesting alternative, dave, but didn’t really fit my needs since I was mostly struggling against iTunes Connect.

Anyway, the problem seems to be solved.

  1. As suggested in the other thread, test IAP using an Ad-hoc Distribution profile.

  2. Make sure you can retrieve the IAP list by using Corona’s sample code for printing an IAP list.

  3. Then the usual stuff:

a. Log out before launching the app

b. Log in only when attempting the purchase

#5

Well, answering part of my own question: 1-3 must be done. I wonder about #4 though - can we test using developer versions?

#6

This probably isn’t a recommended practice, but I tested my IAP’s first on Android, using live code.   I created the IAP, made the product free, uploaded the new version that uses IAP, and tested with a live Google Play account (different than the developer account).    It only takes 90 minutes for a new app to go live on Google Play, so the 2 or 3 revs I had to go through to fix issues wasn’t that big of a deal.   

I had paltry download numbers, so I wasn’t worried about potentially upsetting a large user base.   

Anyway, once I debugged all the issues with my use of the store API, I did the same for iOS.   Fortunately, the IAP interface worked the first time, which I was fairly confident it would since it worked on Android.   

#7

That is a really interesting alternative, dave, but didn’t really fit my needs since I was mostly struggling against iTunes Connect.

Anyway, the problem seems to be solved.

  1. As suggested in the other thread, test IAP using an Ad-hoc Distribution profile.

  2. Make sure you can retrieve the IAP list by using Corona’s sample code for printing an IAP list.

  3. Then the usual stuff:

a. Log out before launching the app

b. Log in only when attempting the purchase