crashlytics

No repository found in Crashlytics install for eclipse

房东的猫 提交于 2019-12-02 23:26:43
I'm trying to install the Crashlytics SDK into my Eclipse but I'm getting the following error: 'Installing Software' has encountered a problem. An error ocurred while collecting items to be installed An error occurred while collecting items to be installed session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No repository found containing: osgi.bundle,com.android.ide.eclipse.adt,22.0.1.v201305230001--685705 No repository found containing: osgi.bundle,com.android.ide.eclipse.adt.package,22.0.1.v201305230001--685705 No repository

crashlytics android studio gradle build failed

最后都变了- 提交于 2019-12-02 23:12:43
I have installed crashlytics plugin to android studio 0.9.3; after this I added to my project; It added lines to gradle, first activity and so on...; after this build fails with this error: Error:Execution failed for task ':app:fabricCleanupResourcesDebug'. Crashlytics Developer Tools error. Here is my gradle file, what should I change ? Crashlytics added it's lines automatically: buildscript { repositories { maven { url 'https://maven.fabric.io/public' } } dependencies { classpath 'io.fabric.tools:gradle:1.+' } } apply plugin : 'com.android.application' apply plugin : 'io.fabric' repositories

Collect logs from system classes

荒凉一梦 提交于 2019-12-02 21:13:35
问题 I'm working on an app that uses Android's MediaMuxer for recording the screen. Using Crashlytics, a significant number of users have the "Failed to stop the muxer" crash, but I can't reproduce it locally on any of my devices. According to another question, the MPEG4Writer logs generated while MediaMuxer is running should indicate what the source of the problem is, but since I'm unable to reproduce it locally, I need to collect those logs remotely and pass them over to Crashlytics. So here's

Send a log to Crashlytics without an app crash

♀尐吖头ヾ 提交于 2019-12-02 19:59:07
How can I get Crashlytics to receive a log without my app crashing? I have the following code: if(!context.managedObjectContext save:&error) { CLS_LOG(@"%@",error.description) } When an error occurs, I want the Crashlytics server to receive the error but the app should continue running. I do not need the log right away. I would be happy to get the log on the next restart. I just do not want to have to trigger a crash in my app to receive the log. Is this possible? Tiago Almeida With the new update from crashlytics you can now use: [[Crashlytics sharedInstance] recordError:error]; And in Swift:

Crashlytics - how can I delete builds/versions?

依然范特西╮ 提交于 2019-12-02 17:49:34
I want to delete 2 of the builds/versions from the Crashlytics dashboard — they were uploaded with the wrong version number and it's creating havoc in the testing process. I would prefer to completely and totally remove them from Crashlytics. Alexizamerican Alex from Fabric here. If you want to archive a version of your app, head to: https://fabric.io/settings/apps Then select your app, click on the Versions tab, and disable any versions you no longer need. You can't technically delete an app, because maybe someone has downloaded it and you want to still receive its crash reports. Hence you

Android - Crashlytics, run code during crash

扶醉桌前 提交于 2019-12-02 17:49:15
问题 I had a bad crash case that was caused due to some Asyncs doing stuff in improper order in a SQLite and thing blew up. It took me some time to debug all that and access to the internal db would have helped immensely. I know how to access that internal db on a dev device but in case something goes wrong I would like to be able to get an instance of that db no matter the device. For error reporting I am using Crashlytics. The question is: Is there a way to have Crashlytics run a piece of code

How to upload a mapping file to Firebase Crashlytics?

[亡魂溺海] 提交于 2019-12-02 16:34:33
In the old Crash reporting - there is easy way to upload. i didn't find it in the Crashlytics section UPDATE: Firebase update their docs: see here There is no need anymore to manually upload mapping file. 1 - To preserve the info Crashlytics needs for readable crash reports, add the following lines to your config file: -keepattributes *Annotation* -keepattributes SourceFile,LineNumberTable -keep public class * extends java.lang.Exception 2 - To let Crashlytics automatically upload the ProGuard or DexGuard mapping file, remove this line from the config file ( app/proguard-rules.pro ):

iOS Error loading your issues in Firebase Crashlytics dashboard

喜你入骨 提交于 2019-12-02 11:43:39
Firebase Crashlytics dashboard error In my Firebase Crashlytics console, I can not see my crash reports. It is saying Error loading.See the above picture for details. My Podfile: platform :ios, '9.0' target 'myproject' do # Comment the next line if you're not using Swift and don't want to use dynamic frameworks use_frameworks! pod 'DatePickerDialog' pod 'Firebase/Core' pod 'Firebase/Messaging' pod 'SQLite.swift', '~> 0.11.5' pod 'SwiftyJSON', '~> 4.1.0' pod 'nanopb' pod 'Fabric', '~> 1.7.11' pod 'Crashlytics', '~> 3.10.7' # Pods for myproject target 'myprojectTests' do inherit! :search_paths #

Collect logs from system classes

一世执手 提交于 2019-12-02 10:25:54
I'm working on an app that uses Android's MediaMuxer for recording the screen. Using Crashlytics, a significant number of users have the "Failed to stop the muxer" crash, but I can't reproduce it locally on any of my devices. According to another question , the MPEG4Writer logs generated while MediaMuxer is running should indicate what the source of the problem is, but since I'm unable to reproduce it locally, I need to collect those logs remotely and pass them over to Crashlytics. So here's my problem: MediaMuxer and MPEG4Writer are system classes, so obviously I can't edit them to add

Fatal signal 11 (SIGSEGV), code 1, fault addr 0x48 in tid 21741 (RenderThread) in android in rear case in some device

感情迁移 提交于 2019-12-02 08:50:52
问题 Fatal signal 11 (SIGSEGV), code 1, fault addr 0x48 in tid 21741 (RenderThread) in occured in the rearest case in some device.If anyone knows please answer.Due to this error android application crash at every activity. <activity android:name=".HomeActivity"/> crash 回答1: Solved. just add: android:hardwareAccelerated="false" in manifest file in activity <activity android:hardwareAccelerated="false" android:name=".HomeActivity"/> Reference: Hardware Acceleration. 来源: https://stackoverflow.com