crashlytics

Crashlytics - how can I delete builds/versions?

由 核能气质少年 提交于 2019-12-03 04:41:07
问题 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. 回答1: 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

How to import only selected native library ABIs from AAR?

由 烈酒焚心 提交于 2019-12-03 04:24:32
I have a bit unusual problem - my Android app contains native libs and I build native libs for armeabi-v7a and x86. However, now I need to integrate a third party library into my app which also contains native libraries (third party library is Crashlytics which I included via Maven from my build.gradle.). The problem is that third party library's AAR provides all arhitectures (armeabi, arm64-v8a, armeabi-v7a, mips, mips64, x86 and x86_64) and my app only supports armeabi-v7a and x86 (arm64-v8a is planned for near future), so when final apk is built it contains 3rd party library's all ABI's and

How to have a callback for when a crash occurred, while using Crashlytics SDK?

由 会有一股神秘感。 提交于 2019-12-03 03:49:59
Background We use Crashlytics SDK to manage app crashes and get needed information about them. So far, the information that the SDK automatically gathered was enough The problem I'd like to add more information for each crash, such as: available&total heap memory, activity stack,... Thing is, I don't see a way to achieve this. I know that the way Android framework works with unhandled exceptions is pretty easy (using Thread.setDefaultUncaughtExceptionHandler ) and it's probably how the SDK works, but I can't find where to use the listener of the SDK itself. What I've tried The SDK has a

How do I use Crashlytics for my React Native Android App?

由 女生的网名这么多〃 提交于 2019-12-03 03:06:28
I am trying to figure out how to use Crashlytics from Fabric for my React Native Android APP. I followed the steps on the Fabric homepage and added some lines in my build.gradle files. But the builds always crash. Is there a difference using Crashlytics for React Native Android and Crashlytics for Native Android development using Android Studio and Java? I got it working in some way, but it may not be the perfect solution... 1: Add fabric/crashlytics into your app/build.gradle - File (I didn´t have the buildscript in my app/build.gradle so i just included it. But i am not sure if this is good.

How to upload a mapping file to Firebase Crashlytics?

由 别说谁变了你拦得住时间么 提交于 2019-12-03 03:01:19
问题 In the old Crash reporting - there is easy way to upload. i didn't find it in the Crashlytics section 回答1: 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

'dependencies' cannot be applied to '(groovy.lang.Closure)'

由 匿名 (未验证) 提交于 2019-12-03 02:59:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: I am unable to fix this error: dependencies cannot be applied to '(groovy.lang.Closure) This is my gradle file: buildscript { repositories { maven { url 'http://download.crashlytics.com/maven' } } dependencies { classpath 'com.crashlytics.tools.gradle:crashlytics-gradle:1.+' } } apply plugin: 'android' apply plugin: 'crashlytics' repositories { maven { url 'http://download.crashlytics.com/maven' } } dependencies { compile fileTree(dir: "$buildDir/native-libs", include: 'native-libs.jar') compile fileTree(dir: 'libs', include: '*.jar')

What is causing this Crashlytics compile warning? (Auto-Linking supplied '…' framework linker option at '…' is not a dylib)

由 匿名 (未验证) 提交于 2019-12-03 02:57:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: Compiling my main target (not a test target like here ) yields this error: ld: warning: Auto-Linking supplied '~/Documents/my_app/MyApp/Crashlytics.framework/Crashlytics', framework linker option at ~/Documents/my_app/MyApp/Crashlytics.framework/Crashlytics is not a dylib From this build command: Ld /Build/Products/Debug-iphonesimulator/MyApp.app/MyApp normal i386 cd ~/Documents/my_app/MyApp export IPHONEOS_DEPLOYMENT_TARGET=8.0 export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:

What is causing this Crashlytics compile warning? (Auto-Linking supplied '…' framework linker option at '…' is not a dylib)

由 匿名 (未验证) 提交于 2019-12-03 02:56:01
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: Compiling my main target (not a test target like here ) yields this error: ld: warning: Auto-Linking supplied '~/Documents/my_app/MyApp/Crashlytics.framework/Crashlytics', framework linker option at ~/Documents/my_app/MyApp/Crashlytics.framework/Crashlytics is not a dylib From this build command: Ld /Build/Products/Debug-iphonesimulator/MyApp.app/MyApp normal i386 cd ~/Documents/my_app/MyApp export IPHONEOS_DEPLOYMENT_TARGET=8.0 export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:

Could not determine the dependencies of task ':app:crashlyticsStoreDeobsDebug' if I enable the proguard

由 匿名 (未验证) 提交于 2019-12-03 02:50:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: I get following error when I was running an app within Android Studio 2. Gradle tasks [:app:assembleDebug] Could not determine the dependencies of task ':app:crashlyticsStoreDeobsDebug'. > Task with path 'dexDebug' not found in project ':app'. BUILD FAILED Here is the build.gradle for module buildscript { repositories { maven { url 'http://download.crashlytics.com/maven' } maven { url "http://dl.bintray.com/populov/maven" } } dependencies { classpath 'com.crashlytics.tools.gradle:crashlytics-gradle:1.+' } } apply plugin: 'com.android

Crashlytics could not find the manifest with fabric.properties

由 匿名 (未验证) 提交于 2019-12-03 02:50:02
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: Im using classpath 'io.fabric.tools:gradle:1.+' and have a fabric.properties inside the module that I use for the fabric plugin. When I run gradlew crashlyticsUploadDistributionProdStaging I get: `Crashlytics could not find the manifest` com.crashlytics.tools.android.project.ManifestData$ManifestIOException: Crashlytics could not find the manifest. Not found at .../app/build/intermediates/manifests/full/prod/staging/AndroidManifest.xml Why? 回答1: It worked after I updated the fabric.properties with the right data and split the commannds:
订阅 crashlytics