I’m trying to test IAP in sandbox.
When I use a new sandbox login, I’m asked to login to itunes within my app twice. Then I get failed.
Working on windows so no easy console info.
I can get ‘print’ info as I use a messagebox function as my replacement.
Any other response from itunes that might help me?
Anyone seen the login twice issue? Is it normal?
Setting IAP in iOS is bit of pain. I have put down some of the steps in this blog.Hope this helps!
http://codebytez.com/in-app-purchases-for-an-iphone-application/
Two logins are not normal. How are you developing for iOS from Windows?
Are you having success getting a list of products from the server? Does this happen when you init the store? When you try and purchase?
Rob
Rob,
Yes, developing from windows. Testing on iPad via corona viewer, but also created a build and same issue.
Haven’t checked on list of products, because there is only one.
I have init and purchase in same handler, Should I have timegap?
Only see the login, nothing else except the fail notice.
You shouldn’t have a purchase until you’re ready to purchase something. Yes, give init time to finish.
What’s not obvious is at what stage of the Apple inapp review process can I test an inapp purchase?
Do I have to wait till Apple have approved?
I don’t want to sound dismissive, but this really isn’t a Corona SDK issue. That is to say, we are no more experts in how to do this than you are. This is purely an Apple issue and your Corona components don’t factor in. Therefore we are probably not the best source of info. There are probably tons of posts out there on the Apple Developer forums or through a Google Search that could help you work out your testing needs. Apple changes the rules too often to keep track of. Used to, you had to submit the app then reject the binary. Then there was a period of where IAP’s were submitted separately from the app and you didn’t have to reject the binary. Now they submit together and maybe you have to reject again. Or maybe its just uploading a version into testFlight.
Rob
Today the Apple rule is that iaps can be tested with a not yet approved binary. The catch is that your first iap has to be approved before you can add more in iTunes connect. Once the first one is approved, you can add as many as you want. So, your first iap and binary must be approved before you can add any more.
Setting IAP in iOS is bit of pain. I have put down some of the steps in this blog.Hope this helps!
http://codebytez.com/in-app-purchases-for-an-iphone-application/
Two logins are not normal. How are you developing for iOS from Windows?
Are you having success getting a list of products from the server? Does this happen when you init the store? When you try and purchase?
Rob
Rob,
Yes, developing from windows. Testing on iPad via corona viewer, but also created a build and same issue.
Haven’t checked on list of products, because there is only one.
I have init and purchase in same handler, Should I have timegap?
Only see the login, nothing else except the fail notice.
You shouldn’t have a purchase until you’re ready to purchase something. Yes, give init time to finish.
What’s not obvious is at what stage of the Apple inapp review process can I test an inapp purchase?
Do I have to wait till Apple have approved?
I don’t want to sound dismissive, but this really isn’t a Corona SDK issue. That is to say, we are no more experts in how to do this than you are. This is purely an Apple issue and your Corona components don’t factor in. Therefore we are probably not the best source of info. There are probably tons of posts out there on the Apple Developer forums or through a Google Search that could help you work out your testing needs. Apple changes the rules too often to keep track of. Used to, you had to submit the app then reject the binary. Then there was a period of where IAP’s were submitted separately from the app and you didn’t have to reject the binary. Now they submit together and maybe you have to reject again. Or maybe its just uploading a version into testFlight.
Rob
Today the Apple rule is that iaps can be tested with a not yet approved binary. The catch is that your first iap has to be approved before you can add more in iTunes connect. Once the first one is approved, you can add as many as you want. So, your first iap and binary must be approved before you can add any more.