Amazon was able to send me the error log from their test of my apps. Would appreciate any debugging help. As I said in an earlier post, these apps all test and run fine on multiple devices. Just can't get past the Amazon test. Here's the error log: 09-11 16:13:16.227 W/ZZ (13372): Creating uscfootball_appDelegate object. 09-11 16:13:16.227 W/ZZ (13372): uscfootball_appDelegate:loadAudioPlayer 09-11 16:13:16.237 W/ZZ (13372): BT_application: Creating root-app object. 09-11 16:13:16.237 W/ZZ (13372): BT_device: Creating root-device object. 09-11 16:13:16.237 W/ZZ (13372): BT_device: This device uses an Android display density of: 240dpi (dots per inch) 09-11 16:13:16.237 W/ZZ (13372): uscfootball_appDelegate:SoundEffectLoader:doInBackground initSoundEffects 09-11 16:13:16.247 W/IccCardProxy(1685): Default IccRecords 09-11 16:13:16.247 W/ZZ (13372): BT_device: This device can send SMS / Text messages. 09-11 16:13:16.247 W/ZZ (13372): BT_device: This device cant make phone calls. 09-11 16:13:16.247 W/ZZ (13372): BT_device: This device can take pictures. 09-11 16:13:16.247 W/ZZ (13372): BT_device: This device can take videos. 09-11 16:13:16.247 W/ZZ (13372): BT_device: This device can send emails. 09-11 16:13:16.247 W/ZZ (13372): BT_device: This device is GPS capable. 09-11 16:13:16.247 W/ZZ (13372): BT_user: Creating root-user object. 09-11 16:13:16.257 W/ZZ (13372): BT_activity_root:onCreate 09-11 16:13:16.267 W/ZZ (13372): uscfootball_appDelegate:SoundEffectLoader:doInBackground initSoundEffects DISABLED 09-11 16:13:16.277 W/dalvikvm(13372): VFY: Lcom/uscfootball/BT_fileManager; is not instance of Landroid/app/Activity; 09-11 16:13:16.277 W/dalvikvm(13372): VFY: bad arg 0 (into Landroid/app/Activity;) 09-11 16:13:16.277 W/dalvikvm(13372): VFY: rejecting call to Lcom/amazon/android/Kiwi;.onActivityResult (Landroid/app/Activity;IILandroid/content/Intent;)Z 09-11 16:13:16.277 W/dalvikvm(13372): VFY: rejecting opcode 0x71 at 0x0000 09-11 16:13:16.277 W/dalvikvm(13372): VFY: rejected Lcom/uscfootball/BT_fileManager;.onActivityResult (IILandroid/content/Intent;)V 09-11 16:13:16.277 W/dalvikvm(13372): Verifier rejected class Lcom/uscfootball/BT_fileManager; 09-11 16:13:16.277 W/dalvikvm(13372): threadid=1: thread exiting with uncaught exception (group=0x40025a70) 09-11 16:13:16.277 E/AndroidRuntime(13372): FATAL EXCEPTION: main 09-11 16:13:16.277 E/AndroidRuntime(13372): java.lang.VerifyError: com.uscfootball.BT_fileManager 09-11 16:13:16.277 E/AndroidRuntime(13372): at com.uscfootball.BT_progressSpinner.show(BT_progressSpinner.java) 09-11 16:13:16.277 E/AndroidRuntime(13372): at com.uscfootball.BT_progressSpinner.show(BT_progressSpinner.java) 09-11 16:13:16.277 E/AndroidRuntime(13372): at com.uscfootball.BT_activity_root.showProgress(BT_activity_root.java) 09-11 16:13:16.277 E/AndroidRuntime(13372): at com.uscfootball.BT_activity_root.onCreateBT_activity_root(BT_activity_root.java) 09-11 16:13:16.277 E/AndroidRuntime(13372): at com.uscfootball.BT_activity_root.onCreate(BT_activity_root.java) 09-11 16:13:16.277 E/AndroidRuntime(13372): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1088) 09-11 16:13:16.277 E/AndroidRuntime(13372): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2802) 09-11 16:13:16.277 E/AndroidRuntime(13372): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2859) 09-11 16:13:16.277 E/AndroidRuntime(13372): at android.app.ActivityThread.access$2300(ActivityThread.java:136) 09-11 16:13:16.277 E/AndroidRuntime(13372): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2179) 09-11 16:13:16.277 E/AndroidRuntime(13372): at android.os.Handler.dispatchMessage(Handler.java:99) 09-11 16:13:16.277 E/AndroidRuntime(13372): at android.os.Looper.loop(Looper.java:143) 09-11 16:13:16.277 E/AndroidRuntime(13372): at android.app.ActivityThread.main(ActivityThread.java:5073) 09-11 16:13:16.277 E/AndroidRuntime(13372): at java.lang.reflect.Method.invokeNative(Native Method) 09-11 16:13:16.277 E/AndroidRuntime(13372): at java.lang.reflect.Method.invoke(Method.java:521) 09-11 16:13:16.277 E/AndroidRuntime(13372): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858) 09-11 16:13:16.277 E/AndroidRuntime(13372): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616) 09-11 16:13:16.277 E/AndroidRuntime(13372): at dalvik.system.NativeStart.main(Native Method) 09-11 16:13:16.287 W/ActivityManager(1568): Force finishing activity com.v1_4.B8BD33E9AAC03563686BD5A6.com/com.uscfootball.BT_activity_root

Seems to me the issue is here: "rejecting opcode 0x71 at 0x0000" This might shed some light...: http://stackoverflow.com/questions/8105805/amazon-java-lang-verifyerror-android

Q1: Did the Amazon review team send you that output, from a LogCat console? If so, cool! My eye immediately went to this line: VFY: Lcom/uscfootball/BT_fileManager; is not instance of Landroid/app/Activity That's an obvious error but why you're getting it is not obvious at all. The BT_fileManager class is for sure NOT an Android Activity. It does not subclass Android Activity. All the "screens" in your app are subclasses of Android's built in Activity class. Each screen in Android is an "Activity." I treat Activities like UIViewControllers in the iOS world. Why their compiler / tool is trying to identify that simple java class (BT_fileManager.java) as an Activity is strange. I followed the URL @raveyd posted and it suggests (a post by someone there) that Amazon injects certain LifeCylce events into apps and changes some things. This of course COULD explain what may be happening. But, I'm not sure what to recommend based on that knowledge? There are lots of class files in your project that are NOT Android Activities. Some are, some are not. The ones that are Android Activities (again, classes that extend the Android Activity class) are listed in your apps AndroidManifest.xml file. Per the Android instructions. Listing each activity used by your app in the manifest is mandatory. Anyone else have any ideas? I'm happy to have a dialogue with the Amazon tech guy if there's a contact email or something? You're free to share my email with them too if you think it will help? Dunno the relationship, never worked with Amazon before.

@MGoBlue, do you need to apply the Amazon DRM? It's not a requirement, unless you have (I think) facebook integration. Without the Amazon DRM your app would be fine.

Thanks guys. @raveyd - I did apply the Amazon DRM. Wonder if that's the issue? I'm going to submit a different app today without the DRM and we'll see if that works. @david - I sent you an email that I received from Amazon with some additional notes. Will be interesting to see how this all works out. Thanks!

@MGoBlue - it's almost certainly the issue. The DRM adds Amazon code to the binary (you can see some in the error log - 'Lcom/amazon/android/Kiwi'). Choosing 'No DRM' will submit your regular binary with no modifications by Amazon. If it's been tested on multiple devices with no issues, it'll be fine.

Thanks. That's good to know. I assumed it was similar to the "copy protection" function on Google Play which I've used about 50% of the time. Wasn't thinking they'd be modifying the code.

Okay, I'm REALLY getting frustrated with Amazon. I've submitted apps now both with and without Amazon's DRM and they've all been rejected with the same cryptic response of "App force closes." @David - I sent them a response based on your post above "That's an obvious error but why you're getting it is not obvious at all. The BT_fileManager class is for sure NOT an Android Activity. It does not subclass Android Activity." Here was their response (again, not very helpful): Thank you for writing back. Our testing team has responded with the following: "We clearly see the class listed as an activity in the manifest. E: activity (line=49) A: android:label(0x01010001)=@0x7f050000 A: android:name(0x01010003)="com.uscfootball.BT_fileManager" (Raw: "com.uscfootball.BT_fileManager") A: android:configChanges(0x0101001f)=(type 0x11)0xa0 A non-activity class has been listed as an activity in the manifest"