Xamarin.Firebase.iOS.Crashlytics issue when uploading symbols on macOS 10.15 "Catalina" #312
Comments
I've met the same issue. As a workaround you can just comment or delete the next line in the Xamarin.Firebase.iOS.Crashlytics.targets file:
|
For now this works for me :) Waiting for fix |
@Dubnovitsky Many thanks for the workaround, and the quick response. Very much appreciated. I'm able to build and test again. |
Oops, sorry, didn't mean to close the issue |
I have a question, if I comment on this line to compile my project, is it possible that I do not record error events in firebase? and this not work for me, it's compile but when I open the app, it closes. |
I don't think the statistics will be saved because the configuration file is commented out. |
This command is just upload dSYM files to Firebase. It's required if you want to see symbolicated crash logs in Firebase console. You can comment this line, compile your application and upload dSYM files to Firebase manually.
@Jmunozg |
Hello, I updated to the latest version of xamarin and the reported error was not presented to me, apparently it was corrected. |
Firebase Crashlytics v3.14.0 has been pushed. The update was tested on Catalina with the following environment of VS4M and seems to be working without a problem:
Also, this update contains two flags that let you have more control over the upload process. For more info, here's the readme file. Best! |
I've just upgraded to macOS 10.15 Catalina, and I'm now getting the following build error:
packages/Xamarin.Firebase.iOS.Crashlytics.3.10.9/build/Xamarin.Firebase.iOS.Crashlytics.targets(53,3): error MSB3073:
The command "'/Users/timauckland2/Library/Caches/XamarinBuildDownload/Fbrc-1.7.13/upload-symbols' -gsp '/Users/timauckland2/Documents/bitbucket/navigatorapp/NavigatorApp.iOS/GoogleService-Info.plist' -p ios 'bin/iPhone/Release/NavigatorApp.iOS.app.dSYM'" exited with code 8.
This looks very similar to issue #194.
Is there a workaround for this problem?
Thanks.
The text was updated successfully, but these errors were encountered: