crashlytics
Could not get crash report in Crashlytics / fabric. Showing error : “It looks like we are missing dSYMs to process crashes for the versions below.”
I have after I complete the Fabric setup successfully into my app, the same issue,I tried every solution but the one that worked for me was: Go to Project settings of the project and target and set Debug Information Format to DWARF with dSYM File Set the current config
Beta from Crashlytics fail to install build on testers’ devices
Perhaps the provisioning profile embedded in the build has been invalidated. Use Xcode to create a new archive, then use Fabric to upload a new build with that archive. Discussion: In my case, I had deleted the provisioning profile in the Apple Developer Member Center that had been embedded in each of my Fabric Beta … Read more
Could not find method create() for arguments – Crashlytics issue
Update: Check Mike’s answer first! Old answer: It looks like Fabric released a new version thats breaks the build for some apps. If you have the line io.fabric.tools:gradle:1.+ (which is recommended by Fabric, but not ideal) you will automatically use the new version. In the meantime you can replace 1.+ with the latest “stable” version … Read more
Crashlytics iOS – log caught exception
Mike from Crashlytics and Fabric here. You can now capture logged NSErrors in your iOS, tvOS, or OS X app. You want to use: [CrashlyticsKit recordError:error]; or Crashlytics.sharedInstance().recordError(error) This will let you capture a fair number of logged NSErrors per user session. These are only sent on app relaunch. Logged errors errors are grouped by … Read more
Error:Gradle: Execution failed for task ‘:app:crashlyticsCleanupResourcesDebug’. > Crashlytics Developer Tools error
You need to add your API Key to the Android Manifest: <application> <meta-data android:name=”com.crashlytics.ApiKey” android:value=”your key here” /> </application>
Send a log to Crashlytics without an app crash
With the new update from crashlytics you can now use: [[FIRCrashlytics crashlytics] recordError:error]; And in Swift: Crashlytics.crashlytics().record(error: error) You can check the documentation here.