Thanks for the response Joshua!
When you say “optional”, do you mean it will still be in the manifest as optional (some optional keyword/syntax)…or will it only be included on an app by app basis if used? Just wanted to better understand…I am sure you all will get it sorted out =) [import]uid: 39506 topic_id: 16102 reply_id: 62213[/import]
“Your app cannot require a gyroscope…”
Ok so if I read this correctly then games like Doodle Jump, and any accelerometer/Gyrobased game will not work?
If that’s the case, then I’m cancelling my order with them. 7 of the 18 games I am working on use those features. I actually plan on doing Android and only on the Kindle Fire, just as I think it might fix some of the fragmentation with all the different devices.
I tried hunting down solid feature information, but I cannot confirm if Kindle Fire supports accelerometer/Gyroscope or not. Seems like just rumor mill sites. Looking at the portion quote above though, that might piss a lot of developers off and not want to develop for it.
Any thoughts? 
(I have a few weeks before I can cancel my pre order heh)
ng [import]uid: 61600 topic_id: 16102 reply_id: 62216[/import]
@joshua, do you think that might make it to the next (or the one after that) daily build?
I’m asking that as my tablet+phone app (submitted last week) is in review and I think I should have the approval/rejection in a day or two.
If it’s rejected, it would be great to be able to recompile & resubmit with that fix included. I’m trying to get it live by halloween… [import]uid: 10478 topic_id: 16102 reply_id: 62217[/import]
Not that I know anything about any of this, but “no gyroscope” doesn’t mean “no accelerometer”. I’m not sure how they could build a tablet without the accelerometer since they need to detect orientation changes.
[import]uid: 19626 topic_id: 16102 reply_id: 62235[/import]
Everyone,
I’ve modified Corona to make the READ_PHONE_STATE permission “optional” per Amazon’s feedback. What that means is that the permission is still set within the AndroidManifest.xml file, but it is not “required”. This will prevent the app from being filtered out from the market place when browsing from an Android Tablet. This should also allow you to pass Amazon’s market place app submission process for tablet-only apps. That said, Kindle Fire support is still a problem and we are still working with Amazon on that (prepares to duck), but it should pass for all other devices.
The above change will be made available in the next daily build #644.
Regarding the accelerometer, the Kindle Fire does that sensor. It just doesn’t haven a gyroscope. See the following link for a list of features that the Kindle Fire supports.
https://developer.amazon.com/help/faq.html#KindleFire
[import]uid: 32256 topic_id: 16102 reply_id: 62246[/import]
Hmmm. Now I’m a bit confused.
Last week I submitted an update for my game Big Fat Goalie to the Amazon app-store. I was using build 2011.638 at the time. It’s a phone+tablet game.
In the ‘what’s new’ section I specifically wrote ‘compatible with Kindle Fire’, not knowing about the issues mentioned in this thread.
The app was approved by Amazon yesterday (oct 19), however after reading the above posts I’m not sure anymore if they actually tested in on the Fire or not. Maybe it got through the approval process only because it was a phone+tablet app?
[import]uid: 70847 topic_id: 16102 reply_id: 62286[/import]
ingemar,
Based on the feedback I’m getting, it appears that apps submitted to support “phone+tablet” pass, but apps that are submitted as tablet-only are being rejected. We believe it had something to do with the READ_PHONE_STATE permission that was set in Corona by default, which is perfectly fine for phones, but tablet aren’t phones. By making that permission not required should allow a tablet-only app to pass now.
I agree that it doesn’t make a lot of sense. Perhaps we’ve found a loop hole in the Amazon submission process. [import]uid: 32256 topic_id: 16102 reply_id: 62292[/import]
I have several apps on Amazon…that have been there for several months as phone/tablet apps. Even though they “were approved” and went live, we got the “incompatible with Fire” email.
So in our case, the phone/tablet apps still failed Fire testing. Maybe others will have better luck…but wanted to share our experience. [import]uid: 39506 topic_id: 16102 reply_id: 62335[/import]
Just to let you know…
As I hoped when this thread started the changes for Kindle Fire seems also to be a good solution for a problem I noticed earlier on the wifi only Samsung Galaxy Tab. Now the builds run on this device (and maybe similar problem boxes) without fiddling in the APKs.
So at last I’m very happy with it!
Thanks ANSCA for fixing it.
[import]uid: 70114 topic_id: 16102 reply_id: 63082[/import]
Here’s a new Kindle Fire rejection issue:
In preparation for the launch of Kindle Fire, we are evaluating each app published in the Amazon Appstore for Android to ensure it provides a high-quality experience on the device. Your existing submission of iTouchiLearn Morning Routines for Preschool Kids has been found to be incompatible with Kindle Fire due to the following:
Apps that run on Kindle Fire do not currently have access to the Google Mobile Services (GMS) of apps and services. If your app currently requires access to GMS apps or services, we recommend that you either remove the features that require these services or modify them to degrade gracefully when invoked (e.g., with an error message such as “This feature is not currently available on this device”). [import]uid: 8780 topic_id: 16102 reply_id: 63268[/import]
I have several apps on Amazon…that have been there for several months as phone/tablet apps. Even though they “were approved” and went live, we got the “incompatible with Fire” email.
for “Nature in Harmony”, recently.
IT was approved, now FIRE email:
In preparation for the launch of Kindle Fire, we are evaluating each app published in the Amazon Appstore for Android to ensure it provides a high-quality experience on the device. Your existing submission of Nature in Harmony HD has been found to be incompatible with Kindle Fire due to the following:
Nature in Harmony HD does not install on Kindle Fire. Please consult the Kindle Fire FAQ for a listing of compatible permissions called in your Android Manifest file, as these may be causing problems with your app’s installation on Kindle Fire. If your app currently lists a permission that is not critical to the functionality or user experience of the application, we recommend that you remove it from your manifest file.
Apps that run on Kindle Fire do not currently have access to the Google Mobile Services (GMS) of apps and services. If your app currently requires access to GMS apps or services, we recommend that you either remove the features that require these services or modify them to degrade gracefully when invoked (e.g., with an error message such as “This feature is not currently available on this device”).
JAD
madlymedia.com
[import]uid: 11151 topic_id: 16102 reply_id: 63290[/import]
We got this too:
Apps that run on Kindle Fire do not currently have access to the Google Mobile Services (GMS) of apps and services. If your app currently requires access to GMS apps or services, we recommend that you either remove the features that require these services or modify them to degrade gracefully when invoked (e.g., with an error message such as “This feature is not currently available on this device”).
Is there a build out there without GMS?
-Angelo [import]uid: 12822 topic_id: 16102 reply_id: 65327[/import]
I submitted our app on October 21st and just heard back. We used build 644 (which had a note “Started working on Kindle Fire support”). The email we got back says:
Your app has been found to be incompatible with Kindle Fire due to the following:
Currently the user is receiving a warning message that states: “Your device is not supported.” The app will then remain in a permanent black screen until closed.
That’s not too helpful, though. Does anyone have a clue?
UPDATE: We resubmitted it last night with the current build. Also removed our orientation detection code and used smaller images. Will have to see if it works. But at this rate, we should get our own Kindle Fire before they get around to checking our code. [import]uid: 9905 topic_id: 16102 reply_id: 65162[/import]
Has this issue been fixed yet and if so what is the solution? [import]uid: 14935 topic_id: 16102 reply_id: 65831[/import]
DavidBFox: I submitted with the same version - 644, and asked for it to be specifically tested with the fire. It was approved, a few days later, but I suspect they didn’t test it with the fire (yet?).
Please keep us updated on what happens with your new submission!
Thanks! [import]uid: 8872 topic_id: 16102 reply_id: 65905[/import]
I got the same email everyone else got. I will resubmit with the latest daily build. [import]uid: 34001 topic_id: 16102 reply_id: 66071[/import]
I just read in the latest daily build: Android: Added Nook and KindleFire support to build scripts
I downloaded it, but I do not see build options to build for Nook and KindleFire. Is this transparent to us? Can we use the Android build option to build for the Nook and KindleFire? Is this support built in? We have been waiting to re-submit our apps for the Kindle Fire and missed the boat on the first shipment.
Thanks. [import]uid: 8780 topic_id: 16102 reply_id: 67825[/import]
Kindle and Nook support is not built in yet. We’re currently putting the infrastructure in place for testing purposes and to support them in the near future. it’s coming… just a lot of work involved to get there. [import]uid: 32256 topic_id: 16102 reply_id: 67836[/import]
Joshua, our app was just accepted into the Amazon Appstore yesterday, but we also got a message a few minutes later saying it was rejected for the Kindle Fire, same as above, because the KF displayed this message on launch: “Your device is not supported.”
Our Kindle Fire arrives on Thursday (yay!), but do you (or does anyone) have any clue what we should be looking for? Is this a Corona issue, or something we might be doing in our code?
Thanks,
David [import]uid: 9905 topic_id: 16102 reply_id: 67837[/import]
David, this is a Corona issue that will soon be solved. [import]uid: 32256 topic_id: 16102 reply_id: 67889[/import]