Has anyone been able to sucessfully test their app in an amazon sandbox environment? We followed the instructions in the sdk; creating a JSON file and downloading the sdk tester. We got the sample file provided by amazon to work, but not the .apk produced by the folio builder.
Adobe support pointed to a flaw on the amazon side. Amazon told us to contact Adobe. So we're left chasing our tail a bit.
If anyone has had success in this test environment, it would be great to know it's possible. And if you have any workarounds or wisdom to share, please do...
So far this has been a pretty horrible experience, with poor support offered by both sides--Adobe & Amazon.
I spent a couple of days toying around with Amazon's In-App purchase documentation, and then finally someone piped up at Amazon and said, "This isn't the process for testing Adobe Air apps."
On Adobe's side, they sent us a .json file that prevented the app from crashing on initial launch, and no further documentation or information regarding what the file was or how it could be modified. Adobe's support directed me to Amazon's documentation, what you linked to, which is wrong for DPS apps, apparently.
What you need is this guy: https://www.box.com/s/c5c54bc0727cf375bb96
It's still pretty poor documentation as far as clearly explaining things go. We've gotten to a point where we can get our retail folio to show up in the app, can purchase it, and it begins downloading (although it throws an error during the purchase process.)
Amazon is investigating further at this point, and I'm still trying to play around with subscription testing, but haven't gotten anywhere. I'll follow-up when we've made progress.
Casey - I talked to a tester on the DPS team, and he says we don't support subscription testing with the Amazon sandbox because it requires fulfillment server-side configurations. We won't be able to support Amazon sandbox testing until we integrate with the new Amazon SDK. I'll update the documentation once DPS supports sandbox testing.
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:
We're building an app for Amazon Kindle Fire that will have no retail folios (or in-app purchases). Instead, we'll simply publish one free folio.
To test, I've been able to install a test viewer on a Kindle Fire, but it crashes (haven't yet set up the .json file).
So, to fix this crashing, seems like some — BUT NOT ALL — of Casey's steps above would apply. Can anyone help confirm/deny these here?
To test a Viewer on Kindle Fire
Step 1.) Build test .apk app. — DONE
Steps 2-6). How necessary are these to test/view an app that has no in-app purchases?
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.
Sending a sample json file would be incredibly helpful! Big thanks, Casey, in advance.
Any ideas what would need to be left in/or taken out of the json file if there are no IAPs?
Re: "You can disregard this" ... Do you mean the pixelated icon? If so, you're saying that it will look just fine in the real app?
Before I added Casey's sample JSON file, I couldn't get past the splashscreen without the app crashing.
So I added the JSON file two ways — one as Casey sent it (with leftover IAP specifics from one of his past projects), one completely empty.
The app now makes it beyond the splashscreen, but when the viewer tries to update the library, the app crashes. This tells me the viewer is trying to reach out to either Adobe and/or Amazon and is finding nothing.
I've published no folios as of yet. Gonna try publishing a folio as public and free. Maybe then the app will see something and not crash.
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.
Josh, I think you're on the right track. I'd repurpose that .json file I supplied. Enter in your Product ID for the published folio where my value was entered, and then switch the price value to "Free." See if that doesn't work.
I didn't test this scenario when I was testing, as we had some retail folios, so I'm not sure exactly what is required to test that scenario out.
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?
Still no dice.
I'm sideloading the .apk file and .json file. Then, I'm launching the app from the SD card folder, which has the .json file at the same level.
So, here's a thought: When I install/launch the app (.apk file), how does the device know to also run the .json file? Should I be naming the .json something specific? Or also launching the JSON file? Or putting the .json file in some sort of subdirectory on the device?