We do not see any app is associated with the developer account that you have posted from. So I am unable to track the app that is causing this strange issue. Please send your app name via ContactUs so that we can investigate the issue further. If you do not have any problem to share your app name publicly in this forum, that would also help us to find our app and investigate the issue. Thanks.
Hi, that's because we "rolled back" to an earlier version of the app so we could get something back on the appstore again without that crash. The latest version would still have this issue. How can we submit new builds without having them be automatically published so we can test the APK you produce after whatever processing is done to our original APK? This way we'd be able to test and ensure that builds aren't broken and released. Additionally, would there be a way to reproduce the processing you do on the APK so I can test it on my builds and try to find the issue?
Believe our application is getting the exact same crash symptoms --
https://forums.developer.amazon.com/forums/thread.jspa?threadID=3903&tstart=0 -- out of curiosity, is the update to your app (the version that had the crashes) using any of these libraries; compile 'com.crashlytics.android:crashlytics:1.+' compile 'uk.co.chrisjenx:calligraphy:1.1.0' compile 'com.github.frankiesardo:icepick:2.3' compile 'com.squareup:otto:1.3.4' compile 'com.squareup.retrofit:retrofit:1.6.1' compile 'com.squareup.okhttp:okhttp:2.0.0' The crash seems to be something to do with annotation processing (based on _Z26dvmGetParameterAnnotationsPK6Method), and these are the libraries we're using that do some heavy lifting with annotations.
From the list you mentioned we use Crashlytics. But we also use RoboGuice which also uses a lot of annotation and reflection. I believe this is where our problems are stemming from, but the interesting part is that we've been using those libraries for a long time and this issue only came about in our latest release. We haven't found a resolution yet. We are still investigating and I'll update here if we find anything.
Will do the same. We broke down and ordered a second tablet (one of the older models that seems to suffer from this crash), so we should hopefully be able to do more in house debugging. Would sure be nice if Amazon provided emulator images for their devices again HINT HINT!
Hi Mauriciovs, We are able to reproduce the issue in 2nd generation Kindle fire devices in the build that you have submitted earlier. We are looking at the issue and will get back once we find any resolution. Thanks.