I'll be working on this this week as well, so I'll be sure to follow-up with my experiences once I've done testing.

Thanks Bob. That would be awesome.

The IAP testing process is scheduled to change completely with V22 with Adobe integrating the new Amazon SDK IAP Tester. I think the process we've been given now by Amazon is a result of the current configuration not really working.

I'll edit this write-up when I'm complete.. but so far it has consisted of:

1. Build test .apk app.
2. Create a .json file, referenced via the guide above. [May not be necessary if you don't want to launch your app until it has been submitted to amazon and they've launched/suppressed the app.]
3. Get a "test" account from amazon. Submit the app, and the in-app purchases you built into your json file. Amazon Suppresses this account/the app from the public.
4. If you side-load the .apk and .json file you can launch the app and test content, but testing purchases will result in receipt verification errors.
5. Include the Amazon shared secret into your DPS Account (Account Administration tool.)
6. Amazon will approve the app/in-app purchases, request your Amazon ID, and distribute the app to you via Cloud on your KF device.
   1. You can then test subscribing/purchasing content, and it should work as desired. No more receipt verification errors.
   2. I'm querying Amazon to then see how you can remove a subscription from your device/account to test other forms of purchasing/subscribing, such as direct entitlement.

Secondly, I've added the three app icons required in App Builder (36x36, 48x48, 72x72). But the resulting app icon on the Kindle Fire home screen looks horribly pixelated.

Any idea why? Is there somewhere else I should be inserting larger icons?

That is a good question. I wouldn't know if you'd need to perform any of those steps. But if it is crashing, that would likely indicate it does require the .json file. I'm not sure that it needs to have legitimate content in it, though. I can send a sample json file if you'd like to try sideloading it.

Yes on the pixelated icon. It looks fine in the real app.

See pm on the .json file.

Still no luck. Publishing a folio set to public and free didn't work.

Feel like we're not in a position to submit to Amazon until we can confirm that this all works (w/ free folio) in the sandbox environment.

I am in a similar situation. I have an app that is ready for submission to both Google and Amazon. I have already submitted the app to Apple. I currently have two folios for this app, a free sample and the first paid issue. I would very much like to test this on an android device to make sure I am submitting an app that works. What I get now is a google app that I can test and won't crash, but I can only see the free folio in the library. The amazon app will start to load then crash, but before it crashes, all I see is the free folio there as well. I am assuming this is because of the issue described in this thread. I have not been able to get a json file with the sdk tester to help with the crashing.

There are a couple issues here. First I can't test the app. Second, I can't submit the app without knowing it will work, and third, Amazon requires a screen capture of what the app looks like after a successful purchase of an in-app folio purchase. How can I provide this to Amazon without being able to get the folio to load in the app while testing? The app has not yet been approved by Apple, but it will be soon and I was able to test both folios on the iPad.

Any suggestions for me?