crash-reports

My application crashes when I try to scroll the tableview very fast or reload the data from remote. Everything seems to be working fine, when I let the remote fetch happen first and then scroll the tableview. I have no idea what the crash log below means. It just works fine sometimes and crashes sometime. Incident Identifier: 710A120C-97E3-45C8-A7B2-E6A7BD98BC1A CrashReporter Key: 8bd54d8428128b9e6b8c04d59b86c40cccf33457 Hardware Model: iPhone5,2 Process: MyApp [5294] Path: /var/mobile/Applications/B6ED5B19-B8D7-4146-90A2-F709AE35292F/MyApp.app/MyApp Identifier: MyApp Version: ??? (???) Code

Background My app has 100% code written in Java, it doesn't need to make any heavy operations. The app itself uses only the next libraries, yet non of them have JNI code: ActionBarSherlock google-play-services_lib The problem Today I got a weird crash report, which doesn't show any normal exception information . The report was sent via a "Galaxy S5 (klte)" device, with Android 4.4 . Here's the crash report title: Native crash at /dev/ashmem/dalvik-jit-code-cache in /dev/ashmem/dalvik-jit-code-cache (deleted) And here is the crash content : *** *** *** *** *** *** *** *** *** *** *** *** *** **

Since the latest builds I'm always getting the following error message when trying to upload the build to Crashlytics. Archive Distribution Error: -3 Could not upload the distribution. The operation couldn't be completed. (HTTP error 422.) I've tried the following: restart Xcode and Fabric plugin rm -rf ~/Library/Caches/com.crashlytics.mac different internet connections (WiFi, mobile) Mike from Fabric here. We had a temporary issue where distributions could not be uploaded. That issue has been resolved, so you should be all set now to distribute now. For reference, the Fabric status page and

I am trying to set user information to crash reports in crashlytics in Android App, so that it will help me to find out which of our users experienced a given crash. I have explored and found there are 3 APIs can set user information in crash report. Those are, void Crashlytics.setUserIdentifier(String identifier); void Crashlytics.setUserName(String name); void Crashlytics.setUserEmail(String email); It is recommended to use all the APIs. All documented at http://support.crashlytics.com/knowledgebase/articles/120548-how-do-i-set-user-information- But I have no idea, 1. How to get user

I am developing an application in which a lot of operations are added in ASINetworkQueue.The operations are basically used for fetching the image from server and then in successful completion set the image in table view cell. Everything is happening fine.I have a button a table view cell on which another view controller gets opened. On that another view there is a cross button on which I pop that view controller. Now when the cross button gets clicked sometimes the app gets crashed there, sometimes it gets crashes when comes back to the previous view and scrolling my table view. When I see the

I have been testing my application with my relatives through distribution via Google Play's alpha testing feature. Crashes have been showing under "Crashes & ANRS" for a while. However, there have been many crashes in the past few days but none have shown up on this page at all. I have spoken with them and they have assured me that there have been crashes and that they have been reporting them and sending them off to Google. Does anyone know why the Crashes & ANRS page on the Google Play Developer Console doesn't pick up these crash reports anymore? I haven't contacted Google about this yet

I recently pushed an iOS 7 update for my application and implemented Flurry Analytics with crash reporting enabled. I recently noticed some users are experiencing crashes. Using Flurry I can retrieve the stack trace at the moment my app crashed to track down the issue. Well, I'm certainly familiar with crash reports and already fixed bugs using them before by getting them from iTunes Connect or mail and simply symbolicating them in Xcode. I however don't succeed at doing that using Flurry. What I tried: When viewing the stack trace on Flurry itself, this is what I get: As you can see, a lot of