question

Hello Surver, Thank you for your inquiry. Unfortunately, our Live App Testing feature only supports Android/FireOS APK file submissions at this time. Which would mean that you wouldn't really be able to test your In-App Purchasing mechanism without using the test environment being configured. Which, for your production app, you should just be able to remove the dependency on the Amazon-Web-App-API-tester.min.js file and the call to amzn_wa.enableApiTester(amzn_wa_tester) in order for your In-App Purchasing implementation to function. The difference between submitting a web app, and submitting an Android/Kindle app would mostly mean what you are submitting. For submission of a web app, you would submit either a URL or a Zip file of resources and a declaration of which HTML file within that zip is your launch page. For submitting an Android/Kindle app, you would be submitting a compiled APK. You could make a web application with a tool such as the Apache Cordova project, which would generate an APK. However, if you did that, you would need to investigate a plugin that integrates Amazon's In-App Purchasing SDK and allows it to be bridged into JavaScript as at this time we do not have support for such plugins directly. Hopefully that answers your questions.

Thankyou DougM - I am now clear about the code to use for the production app. However I am not so clear about your APK comments. Currently I can produce an APK via: Apps & Services -> My Apps -> select the Mobile Web App -> Debug Packages -> hit the '(download) Debug Package' button which produces an APK file - which I had then submitted via the 'Submit App' button. I have 'Current Version (Live)' showing on my dashboard & can search for my app through the Amazon App Store & install it & run it on my mobile device (although I must admit I didn't intend for that to happen until I had finished testing IAP in a live environment). In any case this installed app still seems to run on the SDK tester as the user ID returned from my installed app is same as the SDK user ID. So I guess I have 2 questions: 1. What is the best method for getting my web app into the App Store (if not via the method described above) whilst ensuring that IAP runs in a production environment (i.e. not via SDK tester - I have done all necessary SDK testing) ?, and ... 2. Without using plugins, can I effectively only finalise IAP testing for a Web App once in full production mode (I'm happy to do that if that is what it takes) ? I am happy for you to point me to existing resource in answer to Q 1. - but I have found existing documentation on Web App submission rather confusing. Many thanks Surver

Hello Surver, We would not support doing that. It doesn't mean that it wouldn't work, but since that is not a standard app submission workflow for web apps, we would not be able to guarantee the behavior of what would happen as a result of that app submission.

OK - I hear what you are saying - but I thought the process I described WAS standard app submission process. So I return to my 2 queries: (a) what is the standard app submission process ? & (b) what IAP testing option is available, if any, in a production environment OR can I only test IAP once in production ? many thanks Surver

Well, generally for web apps it really is just submitting the URL or Zip file and walking through the steps to submit it. Doing anything with the debug APK aside from sideloading it on a device would be considered not standard in this case.