Amazon App Store Kindle Fire Issue

Solar2D Android
#61

Until it passes all our internal testing.

Am sure we can release it as is, but if there is bugs and your app crashes, we get the major blunt force trauma for releasing buggy code. If we don’t release, we get the other major blunt force trauma for making you lose money.

So either way, there is no right answer.

The only answer is 42 or wait until all our regression is done.

As you can see from your own testing, it works, so it is close, v close.

And I rather have something that works off the gate than having you bear the cost of being our early adopters unit testers and have nasty one star comments on your app because no matter how good your app is, if it crashes, the nastier the comments will be and the more one star ratings you will get. And even once fixed and the app no longer crahes, you will have that one start lingering rating follow you everywhere you go.
C. [import]uid: 24 topic_id: 13204 reply_id: 67842[/import]

#62

Read this and build for Kindle Fire :slight_smile:
http://www.base2solutions.com/walkabout/Corona%20Tips.html#7 [import]uid: 12704 topic_id: 13204 reply_id: 67899[/import]

#63

So, does Corona support the Nook? We’re looking at the Nook as one of our initial platforms so this support will help us to decide to go with Corona or not.

Also - can you explain the difference between “Added Nook and KindleFire support to build scripts” and “Not the option to build for Fire/Nook”. Either these devices are supported or they aren’t.

Thanks [import]uid: 104904 topic_id: 13204 reply_id: 68113[/import]

#64

What they mean by “Added Nook and KindleFire support to build scripts” is that they’ve added support to their internal build-scripts for these devices.

As I understand there will be additional configuration settings that you can add to your build.settings file to configure how things will be built.
These settings will be revealed once official support is announced for these devices.

From what I’ve heard they seem to be close to the official announcement of Nook/KindleFire support. [import]uid: 70847 topic_id: 13204 reply_id: 68123[/import]

#65

I saw a video on the website that demonstrates the Nook working so this issue is still unclear.

Also, I get what you’re saying Ingemar but I’d still like to understand what Carlos meant by “Added Nook and KindleFire support to build scripts” and “Not the option to build for Fire/Nook”. [import]uid: 104904 topic_id: 13204 reply_id: 68190[/import]

#66

Well, the way I see it is that he’s just saying this:

  1. The functionality to build for the Nook/KindleFire is there (included in their build-scripts).

  2. You will not be able to build for these devices yet since you need to modify your build settings. Hence the “Not the option to build for Fire/Nook”.
    These settings will only be announced once they consider the release final.

There were so many people who thought that the first statement meant that they could just compile with the latest Corona-build and have their apps compatible with Nook/Fire, but that’s not the case. [import]uid: 70847 topic_id: 13204 reply_id: 68200[/import]

#67

Well the confusion is understandable given the way it was written. Hopefully your interpretation is correct - it seems you are taking an educated guess.

Have you seen anywhere mention of when if will be made available?

Thanks. [import]uid: 104904 topic_id: 13204 reply_id: 68202[/import]

#68

@ingemar : correct!

@dan56: any minute now… [import]uid: 24 topic_id: 13204 reply_id: 68204[/import]

#69

Drumroll… [import]uid: 70847 topic_id: 13204 reply_id: 68205[/import]

#70

BTW, our app was accepted into the Amazon Appstore even though it still fails on the Kindle Fire. So earlier information on this thread wasn’t accurate (or at least it’s no longer accurate). I asked about this and was told that they’ll just prevent KF owners from downloading it until it passes their tests, but other Android device owners can buy it. [import]uid: 9905 topic_id: 13204 reply_id: 68422[/import]

#71

C’mon, ansca give us build for Fire option asap. If you want to build it right now just do it manualy!!! I give you working solution on this forum some time ago. [import]uid: 12704 topic_id: 13204 reply_id: 68428[/import]

#72

Update

http://blog.anscamobile.com/2011/11/lighting-the-amazon-kindle-fire/

c
[import]uid: 24 topic_id: 13204 reply_id: 68432[/import]

#73

One of the latest daily builds added the option to build for Amazon/Kindle. Does this mean we can now submit our apps for the Kindle Fire?

Thanks. [import]uid: 8780 topic_id: 13204 reply_id: 69369[/import]

#74

Yep, you can read Carlos’ blog post above: #71 [import]uid: 70847 topic_id: 13204 reply_id: 69372[/import]

#75

Jane,

Yes, the newest daily build now supports Kindle Fire. We’ve also added some new build.settings options that we haven’t documented yet that allows you to control some AndroidManifest.xml settings.

You can now add an entry for “supports-screens”. This allows you to control what size display your app is built for, such as tablet size only, and the market place will filter your app accordingly. I’m sure you’d be interested in this since you make a tablet only app.
http://developer.android.com/guide/topics/manifest/supports-screens-element.html

So an example of the above would like something like this in Corona’s build.settings file…

[lua]settings =
{
android =
{
supportsScreens =
{
smallScreens = false,
},
},
}[/lua]

The entries that you provide to the “supportsScreen” table must exactly match the XML attribute names and values indicated in the Android documentation. So go ahead and give it a go. [import]uid: 32256 topic_id: 13204 reply_id: 69426[/import]

#76

If i can ask, the android:requiresSmallestWidthDp is supported in the last daily build?

Thanks [import]uid: 44965 topic_id: 13204 reply_id: 69728[/import]

#77

Joshua:

Kindle Fire app submission rejected do to following reason:

>>
iTouchiLearn Words for Preschool Kids v 2.0 closes immediately on launch when tested for compatibility on Kindle Fire. We have attached a logcat file to this email to assist you in troubleshooting the problem.
<<

Here’s some insight from the logcat file:

>>
11-25 09:59:35.429 D/dalvikvm( 6392): Note: class Landroid/opengl/GLWrapperBase; has 211 unimplemented (abstract) methods
11-25 09:59:35.523 D/dalvikvm( 6392): GC_FOR_MALLOC freed 196K, 44% free 3386K/6023K, external 847K/1181K, paused 30ms
11-25 09:59:35.523 I/dalvikvm-heap( 6392): Grow heap (frag case) to 6.883MB for 397288-byte allocation
11-25 09:59:35.570 W/dalvikvm( 6392): JNI WARNING: 0x405e8fe8 is not a valid JNI reference
11-25 09:59:35.570 W/dalvikvm( 6392): in Lcom/ansca/corona/JavaToNativeShim;.nativeResize (Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;III)V (ReleaseByteArrayElements)
11-25 09:59:35.578 I/dalvikvm( 6392): “GLThread 12” prio=5 tid=11 RUNNABLE
11-25 09:59:35.578 I/dalvikvm( 6392): | group=“main” sCount=0 dsCount=0 obj=0x4057eab0 self=0x218138
11-25 09:59:35.578 I/dalvikvm( 6392): | sysTid=6403 nice=0 sched=0/0 cgrp=default handle=2195600
11-25 09:59:35.578 I/dalvikvm( 6392): at com.ansca.corona.JavaToNativeShim.nativeResize(Native Method)
11-25 09:59:35.578 I/dalvikvm( 6392): at com.ansca.corona.JavaToNativeShim.resize(JavaToNativeShim.java:-1)
11-25 09:59:35.578 I/dalvikvm( 6392): at com.ansca.corona.CoronaRenderer.onSurfaceChanged(CoronaRenderer.java:-1)
11-25 09:59:35.578 I/dalvikvm( 6392): at android.opengl.derived.SwapGLSurfaceView$GLThread.guardedRun(SwapGLSurfaceView.java:-1)
11-25 09:59:35.578 I/dalvikvm( 6392): at android.opengl.derived.SwapGLSurfaceView$GLThread.run(SwapGLSurfaceView.java:-1)
11-25 09:59:35.578 I/dalvikvm( 6392):
11-25 09:59:35.578 E/dalvikvm( 6392): VM aborting
11-25 09:59:35.578 D/dalvikvm( 6392): GC_FOR_MALLOC freed 1K, 42% free 3772K/6471K, external 847K/1181K, paused 34ms
…
11-25 09:59:36.554 I/DEBUG ( 6335): debuggerd committing suicide to free the zombie!
11-25 09:59:36.554 E/InputDispatcher( 1378): channel ‘407bd058 com.staytoooned.children.iTouchiLearnWords/com.ansca.corona.CoronaActivity (server)’ ~ Consumer closed input channel or an error occurred. events=0x8
11-25 09:59:36.554 E/InputDispatcher( 1378): channel ‘407bd058 com.staytoooned.children.iTouchiLearnWords/com.ansca.corona.CoronaActivity (server)’ ~ Channel is unrecoverably broken and will be disposed!
11-25 09:59:36.554 I/DEBUG ( 6412): debuggerd: Nov 11 2011 22:06:35
11-25 09:59:36.562 I/ActivityManager( 1378): Process com.staytoooned.children.iTouchiLearnWords (pid 6392) has died.
11-25 09:59:36.578 I/WindowManager( 1378): WIN DEATH: Window{407f8858 SurfaceView paused=false}
11-25 09:59:36.578 I/WindowManager( 1378): WIN DEATH: Window{407bd058 com.staytoooned.children.iTouchiLearnWords/com.ansca.corona.CoronaActivity paused=false}
11-25 09:59:36.585 D/Zygote ( 1294): Process 6392 terminated by signal (11)

<<

I tested the app on the Kindle Fire prior to submission and it worked perfectly.

I can post the entire log file if it might be helpful or I can upload the APK. Please help!!

Thanks. [import]uid: 8780 topic_id: 13204 reply_id: 69752[/import]

#78

I see you just posted an update to fix this problem. Thanks! [import]uid: 8780 topic_id: 13204 reply_id: 69778[/import]

#79

Jane,
Yes… the issue that Amazon reported is now fixed as of build #695.

wallac3.gromit,
Yes… the requiresSmallestWidthDp attribute is supported. In fact, the build system will take any value/pair that you provide to the supportsScreens table “as is” and writes it to the AndroidManifest.xml file’s supports-screens tag (although I haven’t personally tested all attributes to see their affects yet).
You would set it up as follows.

[lua]settings =
{
android =
{
supportsScreens =
{
requiresSmallestWidthDp = 600,
},
},
} [/lua]

My understanding is that this setting is used as a marketplace filter that you can use, for example, to prevent small screen devices from purchasing an app that requires a large screen. However, Google’s documentation states that the Android Marketplace currently ignores this setting and recommends that you use the smallScreens attribute too. Please see the below link.

http://developer.android.com/guide/topics/manifest/supports-screens-element.html
[import]uid: 32256 topic_id: 13204 reply_id: 69797[/import]

#80

@Joshua

Thanks [import]uid: 44965 topic_id: 13204 reply_id: 69864[/import]