firebase-crash-reporting

来源： https://stackoverflow.com/questions/63089606/when-im-doing-an-incremental-build-in-android-studio-firebase-crashlytics-cras

来源： https://stackoverflow.com/questions/63089606/when-im-doing-an-incremental-build-in-android-studio-firebase-crashlytics-cras

问题 I'm trying to upload native symbols for external native library in Android app. All setup and it seems the crashlyticsUploadSymbolsRelease succeeded. I checked the crashlytics.log and it says that the .cSYM file 's being generated and uploaded to https://cm.crashlytics.com/api/v3/platforms/android/code_mappings. But when I check the Crashlytics tab in the Firebase console the logs are not resolved i.e. no stack traces to be shown. I use LLD as default. I thought that this could be the problem

问题 I just integrated the new Firebase SDK following these instructions: https://firebase.google.com/docs/crashlytics/get-started-new-sdk It's working with debug builds, but I get this exception on release build: java.io.IOException: com.google.firebase.crashlytics.buildtools.exception.CrashlyticsOrgIdException: Could not fetch Crashlytics Org Id Any idea? 回答1: I was having the same error when trying to build a release APK, but it wasn't going away. I realized that you need to generate at least

问题 We have just integrated firebase, and all of a sudden our deep links are no longer working. We're using AppAuth for authentication, so we're reliant on deep links to direct us to the right place. I'm getting the following error: <Debug> [Firebase/Analytics][I-ACS023001] Deep Link does not contain valid required params. URL params: {...} Initialization of firebase as follows: let bundleId = Bundle.main.bundleIdentifier let filePath = Bundle.main.path(forResource: "GoogleService-Info-" +

问题 Is it possible, to use two different accounts for two different services of google in an Android app? I want to use Google Analytics with Account customer@gmail.com and Firebase Crashreport with Account developer@gmail.com. I get two google-services.json with different project_info values and can't combine them. The solution for different flavours is not relevant as I understand this, because I want to use 2 configuration files for the same flavour (release). 回答1: You can't split between

问题 I have implemented FCM and Firebase analytics with success in my project but I found an error trying with Firebase crash reporting and I don't have any idea what I'm missing. I'm just trying to use Firebase crash reporting following the official tutorial and getting this error: It said: Server did not receive report: Origin Error message: Requests from this Android client application com.xxxxxx are blocked . After dig in google and here (stack overflow), I found some related questions ( link

问题 I added firebase crash reporting to my iOS project (added pod, added build phase script, added json to project, ...). When i run my app, i see in my console: Firebase Crash Reporting: Successfully enabled For testing, i insert fatalError() in my code after my FIRApp.configure() code (as suggested here: https://firebase.google.com/docs/crash/ios#create_your_first_error). No crash reports are sent at my next app launch (that doesn't crash). I see nothing in my xcode console and nothing in my

问题 When a crash gets uploaded to the firebase dashboard it always shows the message Upload symbol file to symbolicate future stack traces for UUID ******* . However I did make sure that the symbol files got uploaded by looking in the Symbol Files tab. Something I noticed though was that the symbol files had a different UUID then what the message on the crash said. What might I be doing wrong here? Something strange is that it seems like neither the UUID in uploaded symbol files nor in the

问题 I followed the guide located here:https://firebase.google.com/docs/crash/ios But when I'm done and attempt to build, I get the following error: /Users/--/Desktop/Test2/Pods/FirebaseCrash/upload-sym-util.bash:349: error: symbolFileUploadLocation: The caller does not have permission Anyone have any ideas? I've searched on google, stack overflow and google groups and don't see anyone else stating this issue that I can find. Running 10.11.5, Xcode 7.3.1 When I open the source for the error, it