Skip to main content
September 13, 2013
Question

Troubles with development profile / testing on iPAD

  • September 13, 2013
  • 1 reply
  • 381 views

Our most recent app has in-app purchases. We got Milkman Games In-App Purchase iOS extension and it seems to be working fine, but I hit a snag on the testing process.

1) on itunes connect, I set up a listing for my app, and created 3 products for it (Non-Consumable type). The app is in the Prepare for Upload status and the products are in the

Ready to Submit status.

2) still on itunes connect I created a test user.

3) on developer.apple.com I created a development provisioning profile for the app. I generated it to run on our previously added test devices.

4) on flash builder 4.6 I compiled the app using the development profile. It compiles successfully.

5) on my iPad, I log off itunes.

6) still on flash builder, I set the app to debug on a device, connect my iPad to my mac and transfer it to the iPad via itunes.

7) the app runs on the iPad on debug mode. I see the debug messages on Flash Builder as the app runs on the device. The first sign of something wrong is when a request to validate the product codes returns an "invalid product" error.

😎 when I try to purchase a product anyway, I get a "purchase failed" event, telling me that the app couldn't connect with the iTunes Store.

What's missing here? The guides, both Milkman's and Adobe's, tell me to transfer the development provisioning profile to the iPad too. I think this is done on iTunes, but unlike with the app, I don't seem to have a visual confirmation that the file is there. The guides say that when I try to connect with the store, the device should call a login box where I can login with the test user created on step 2, but that didn't happen.

I'm stumped here and could use some help. Any ideas? The app is running with air 3.5 but I can set it to work with 3.6 or 3.7 if this helps.

Best regards,

This topic has been closed for replies.

1 reply

Colin Holgate
Inspiring
September 13, 2013

I have seen the same thing you are seeing, and found a solution online somewhere. It turned out that you need to delete the old version of the app from the iPad before trying your new version. Then hopefully things will work.