Amazon App Store Kindle Fire Issue

Solar2D Android
#41

Joshua,

Any news on the Amazon issue? I just saw this on another thread:

[text]I just got a response from Amazon that states:

“Could you please change your permission read_phone_state to optional if it’s not required for your app?”.

I did some searching…but am not finding how to make a permission optional…anyone know if this is possible and/or what the manifest entry would look like?

Also, I opened a bug ticket with Ansca on this.[/text]

Here’s the link:

https://developer.anscamobile.com/forum/2011/10/08/amazon-kindle-fire-warning [import]uid: 8780 topic_id: 13204 reply_id: 62093[/import]

#42

Jane,

We took care of the READ_PHONE_STATE issue and set it up to not be required by the device. That should allow the a tablet-only app to pass the Amazon app submission process. Please the link below for more details…
https://developer.anscamobile.com/forum/2011/10/08/amazon-kindle-fire-warning#comment-62246
[import]uid: 32256 topic_id: 13204 reply_id: 62249[/import]

#43

Joshua,

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”).

Please help! [import]uid: 8780 topic_id: 13204 reply_id: 63267[/import]

#44

Joshua,

I just noticed that Build 645 still states:

android.permission.READ_PHONE_STATE

when you submit the app to Amazon.

Is there something special we need to do?

Thanks [import]uid: 8780 topic_id: 13204 reply_id: 63270[/import]

#45

My app “Nature in Harmony” was approved a few days ago, Now this email for the FIRE:

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: 13204 reply_id: 63292[/import]

#46

Jane, videotv,

Yes, we are still including the READ_PHONE_STATE permission, but now it is flagged as “not required” which will allow the app to pass for tablets. We made this change in build 644. We have also removed the Google Maps library since build 641. So if you submit an app with build 644, then it should pass Amazon’s submission process. Our “Corona Indie Bundle” managed to pass the Amazon submission process.

Currently, Corona apps will pass for all device except the Kindle Fire. So my advice is to submit the app to Amazon without Kindle Fire support at the moment. This is because it is looking like that we may have to build apps differently to support that device. Especially since Amazon will not allow apps that are built with Google Mobile Services. Even our own Corona Indie Bundle is not available for Kindle Fire… just yet. [import]uid: 32256 topic_id: 13204 reply_id: 63297[/import]

#47

Surely, if you’re developing an app for Android tablets, you need to have at least one tablet of your own to test it on? Mind you, quite how I’m going to get hold of a Kindle Fire from the UK I don’t know… [import]uid: 95579 topic_id: 13204 reply_id: 63766[/import]

#48

Joshua, I’m just following up to find out if you have created an “Amazon Kindle Fire” build. Amazon was planning on including apps that were submitted on or before October 31st in the Kindle Fire launch. Please update us on the progress. Thanks. [import]uid: 8780 topic_id: 13204 reply_id: 64694[/import]

#49

Hello Jane,

We’re working on a new “Amzona” or “Kindle Fire” build process now, but unfortunately it won’t be ready by the Oct 31st cut-off. Based on the feedback we’re getting from Amazon, apps that don’t pass for Kindle Fire will not be accepted on their app store, even if you’re not targeting the Kindle Fire. This means no Google Maps, no Google In-App purchases, and we’ll need to provide Corona developers the ability to make permissions optional in the AndroidManifest.xml file for things the Kindle Fire does not have. We are targeting to get this done sometime in November. We definitely see the importance of having Corona supported/running on the Kindle Fire. [import]uid: 32256 topic_id: 13204 reply_id: 64712[/import]

#50

Hmm, I just built Walkabout with 645, and manually edited its manifest. I uploaded it to amazon with specific instructions that it was in response to the Kindle Fire issue in their email - and to only approve it after testing on the Kindle Fire.

The app was approved on Friday. Maybe they didn’t test on the Kindle Fire. [import]uid: 8872 topic_id: 13204 reply_id: 64788[/import]

#51

kam, what did you remove from the AndroidManifest.xml file? [import]uid: 32256 topic_id: 13204 reply_id: 64792[/import]

#52

This whole issue is making me somewhat confused.

I have one app on the Amazon Appstore since August this year, and I haven’t received any emails from them stating that my app isn’t compatible with the Kindle Fire.
However, with the recent discussions about Android permissions, I decided to re-submit my app to Amazon just to be safe.

Last week I recompiled with 648 (with no manual modifications to the manifest), and in the Testing Directives to Amazon, I specifically asked them to test on the Fire and get back to me if any issues were found. The app was approved on Friday.

Maybe it was approved because it’s phone+tablet, maybe the approval process is inconsistent, I have no idea. I guess I’ll just need to wait and see what happens on November 15. [import]uid: 70847 topic_id: 13204 reply_id: 64795[/import]

#53

Josh, here’s the full story with the manifest files…

The existing build on the Amazon store was with Corona Build #319, so that I could also support ARM6. I modified the manifest file as follows:

<?xml version="1.0" encoding="UTF-8"?>  
<manifest package="com.base2.walkaboutb" android:versioncode="260" android:versionname="2.6.0" android:installlocation="auto"> xmlns:android="http://schemas.android.com/apk/res/android"&gt;<br> <application android:theme="@android:style/Theme.NoTitleBar" android:label="@string/app_name" android:icon="@drawable/icon"><br> <activity android:label="@string/app_name" android:name=".MyCoronaActivity" android:launchmode="singleInstance" android:screenorientation="landscape"><br> <intent-filter><br> <action android:name="android.intent.action.MAIN"></action><br> <category android:name="android.intent.category.LAUNCHER"></category><br> </intent-filter><br> </activity><br> </application><br> <uses-sdk android:minsdkversion="6"></uses-sdk><br> <uses-sdk android:targetsdkversion="11"></uses-sdk><br> <supports-screens android:anydensity="true" android:smallscreens="true" android:normalscreens="true" android:largescreens="true" android:xlargescreens="true"></supports-screens><br></manifest>

I received an email from amazon stating the following error with the Kindle fire:

“Use of the Settings Soft Keys (Top menu bar such as volume, device options, etc) causes the app to exit.”

I assumed this was due to some quirk with the old corona since there was zero handling of hardware keys. So I decided to just drop ARM6 and move to the latest build. I re-built using build #645 and used the following manifest file:

  
<?xml version="1.0" encoding="utf-8"?>  
<manifest package="com.base2.walkaboutb" android:versioncode="8261" android:versionname="2.6.1" android:installlocation="auto"> xmlns:android="http://schemas.android.com/apk/res/android"&gt;<br> <application android:label="Walkabout" android:icon="@drawable/icon" android:debuggable="true"><br> <activity android:theme="@android:style/Theme.NoTitleBar.Fullscreen" android:label="Walkabout" android:name="com.ansca.corona.CoronaActivity" android:launchmode="singleTask" android:screenorientation="landscape" android:configchanges="keyboardHidden|orientation"><br> <intent-filter><br> <action android:name="android.intent.action.MAIN"></action><br> <category android:name="android.intent.category.LAUNCHER"></category><br> </intent-filter><br> </activity><br> <activity android:theme="@android:style/Theme.NoTitleBar.Fullscreen" android:name="com.ansca.corona.CameraActivity" android:screenorientation="portrait" android:configchanges="keyboardHidden|orientation"></activity><br> <activity android:theme="@android:style/Theme.NoTitleBar.Fullscreen" android:name="com.ansca.corona.VideoActivity" android:screenorientation="landscape" android:configchanges="keyboardHidden|orientation"></activity><br> <provider android:name="com.ansca.corona.FileContentProvider" android:authorities="com.base2.walkaboutb.files"></provider><br> </application><br> <uses-sdk android:minsdkversion="8"></uses-sdk><br> <uses-sdk android:targetsdkversion="11"></uses-sdk><br> <supports-screens android:anydensity="true" android:smallscreens="true" android:normalscreens="true" android:largescreens="true" android:xlargescreens="true"></supports-screens><br></manifest>

I added a note under ‘Testing Instructions’:

"Please test specifically on Kindle Fire. This is a build in response to issues described in your test report: “Use of the Settings Soft Keys (Top menu bar such as volume, device options, etc) causes the app to exit.”

And the app was approved a few days later. [import]uid: 8872 topic_id: 13204 reply_id: 64796[/import]

#54

Has this been resolved, does Corona officially publish to Kindle Fire without any hackery? [import]uid: 4596 topic_id: 13204 reply_id: 66871[/import]

#55

We are going to ship new bits after the Fire ships, see my tweeter for release dates
c. [import]uid: 24 topic_id: 13204 reply_id: 66873[/import]

#56

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: 13204 reply_id: 67824[/import]

#57

staytooned “Added Nook and KindleFire support to build scripts”

correct, build scripts.

Not the option to build for Fire/Nook.

There is plenty of time for submitting for Fire. We are in constant communication with Amazon and plenty of time.

C.

[import]uid: 24 topic_id: 13204 reply_id: 67827[/import]

#58

Ok It seems that my App does not work for Kindle Fire as previously expected.

With the latest build of 683 I managed to install it on the Kindle Fire and get it to work except one thing it comes up with the ‘Corona SDK Trial’ message. Other than that the app works fine on the Kindle Fire.

I tried again thinking I compiled with the debug key but nope same thing.

The same file installs on my Galaxy Tab with no problems.

What gives? [import]uid: 8697 topic_id: 13204 reply_id: 67838[/import]

#59

*NO*

Read :: Kindle Fire is not supported yet. It will be as soon as we have a device to run all our tests against.

Until we have a device to test against and it passes all the test that it needs to, we will turn it on.

Building for Android 2.2 is not the same as building for Amazon Fire. Trust us***

C.

[import]uid: 24 topic_id: 13204 reply_id: 67839[/import]

#60

And when do you think that will be? Did you not order one on the first day of pre-ordering? Most people got their’s today.

It must be almost done now because I can get the App to run on the Kindle Fire with no problems except for the SDK message, whatever was making it report that it’s not compatible is no longer there.

My App is currently highly visible (#2 on the Entertaiment paid apps and #28 on the All Paid apps) and it is a seasonal App and everyday it’s not on the Kindle Fire is potential lost sales. [import]uid: 8697 topic_id: 13204 reply_id: 67840[/import]