Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

DSYM files successfully uploaded to Firebase but still "missing" in the Firebase Crashlytics Console #403

Open
jonathanfontaine opened this issue Apr 30, 2020 · 6 comments

Comments

@jonathanfontaine
Copy link

Hi,

I'm having trouble with Xamarin.Firebase.iOS.Crashlytics : crashes on the Firebase Console are obfuscated because "mandatory DSYMs files are missing" :

image

  • The GoogleService-Info.plist file is in the root directory and I've downloaded it from Firebase Console

  • According to the readme.txt file, I've added the following lines in my .csproj file :

<PropertyGroup>
    <FirebaseCrashlyticsUploadSymbolsEnabled>True</FirebaseCrashlyticsUploadSymbolsEnabled>
</PropertyGroup>
  • I've also builded on Release and here is the build output I got (everything seems OK ?) :
chmod +x upload-symbols
MyFolder\packages\Xamarin.Firebase.iOS.Crashlytics.3.14.0.1\build\Xamarin.Firebase.iOS.Crashlytics.targets(71,3): warning MSB3098: "Exec" task received an invalid value for the "StdOutEncoding" parameter.
MyFolder\packages\Xamarin.Firebase.iOS.Crashlytics.3.14.0.1\build\Xamarin.Firebase.iOS.Crashlytics.targets(71,3): warning MSB3098: "Exec" task received an invalid value for the "StdErrEncoding" parameter.
'./upload-symbols' -gsp './GoogleService-Info.plist' -p ios './bin/iPhone/Release//My.iOS.App.dSYM'
Successfully submitted symbols for architecture arm64 with UUID 778d7b513b23382796b09a7272278371 in dSYM: /Users/Me/Library/Caches/Xamarin/mtbs/builds/App.iOS/59070d72d5ff161f923dfd59a920ebce/bin/iPhone/Release/My.iOS.App.dSYM[0m
Successfully submitted symbols for architecture armv7 with UUID 61b9623b72423d00a0dc5f658a366a1c in dSYM: /Users/Me/Library/Caches/Xamarin/mtbs/builds/App.iOS/59070d72d5ff161f923dfd59a920ebce/bin/iPhone/Release/My.iOS.App.dSYM[0m
[32mSuccessfully uploaded Crashlytics symbols[0m
MyFolder\packages\Xamarin.Firebase.iOS.Crashlytics.3.14.0.1\build\Xamarin.Firebase.iOS.Crashlytics.targets(74,3): warning MSB3098: "Exec" task received an invalid value for the "StdOutEncoding" parameter.
MyFolder\packages\Xamarin.Firebase.iOS.Crashlytics.3.14.0.1\build\Xamarin.Firebase.iOS.Crashlytics.targets(74,3): warning MSB3098: "Exec" task received an invalid value for the "StdErrEncoding" parameter.
  • I thrown an exception in the ViewWillAppear() method in HomeViewController.cs class like this :
throw new Exception("hello");
  • Here is the stacktrace I got in the Firebase Console : It's obfuscated !

image

Could you please help me to get full and readable iOS stacktraces in Firebase Console ?

@devWaleed
Copy link

Bump

@bash862
Copy link

bash862 commented Jul 27, 2020

I have the same 4 warning during build the release version with the V 3.14.0.3 of the Xamarin.Firebase.iOS.Crashlytics.
build output:
1>chmod +x upload-symbols
1>......\packages\Xamarin.Firebase.iOS.Crashlytics.3.14.0.3\build\Xamarin.Firebase.iOS.Crashlytics.targets(73,3): warning MSB3098: "Exec" task received an invalid value for the "StdOutEncoding" parameter.
1>......\packages\Xamarin.Firebase.iOS.Crashlytics.3.14.0.3\build\Xamarin.Firebase.iOS.Crashlytics.targets(73,3): warning MSB3098: "Exec" task received an invalid value for the "StdErrEncoding" parameter.
1> './upload-symbols' -gsp './GoogleService-Info.plist' -p ios './bin/iPhone/Release/.......app.dSYM'
1> Successfully submitted symbols for architecture arm64 with UUID b11a0a880e2b3ca89137843341116257 in dSYM: ....../a604424c0567088a5309431eebc1bc2e/bin/iPhone/Release/.......app.dSYM�[0m
1> Successfully submitted symbols for architecture armv7 with UUID a01cd01a2b1032129c20ec3cbf7f9007 in dSYM: ....../a604424c0567088a5309431eebc1bc2e/bin/iPhone/Release/.......app.dSYM�[0m
1> �[32mSuccessfully uploaded Crashlytics symbols�[0m
1>......\packages\Xamarin.Firebase.iOS.Crashlytics.3.14.0.3\build\Xamarin.Firebase.iOS.Crashlytics.targets(76,3): warning MSB3098: "Exec" task received an invalid value for the "StdOutEncoding" parameter.
1>......\packages\Xamarin.Firebase.iOS.Crashlytics.3.14.0.3\build\Xamarin.Firebase.iOS.Crashlytics.targets(76,3): warning MSB3098: "Exec" task received an invalid value for the "StdErrEncoding" parameter.

@polieadie
Copy link

I have the following Output.

2> chmod +x upload-symbols
2>C:\Users\rcervantes.nuget\packages\xamarin.firebase.ios.crashlytics\3.14.0.3\buildTransitive\Xamarin.Firebase.iOS.Crashlytics.targets(73,3): warning MSB3098: "Exec" task received an invalid value for the "StdOutEncoding" parameter.
2>C:\Users\rcervantes.nuget\packages\xamarin.firebase.ios.crashlytics\3.14.0.3\buildTransitive\Xamarin.Firebase.iOS.Crashlytics.targets(73,3): warning MSB3098: "Exec" task received an invalid value for the "StdErrEncoding" parameter.
2> './upload-symbols' -gsp './GoogleService-Info.plist' -p ios './bin/iPhone/Release//....iOS.app.dSYM'
2> Successfully submitted symbols for architecture arm64 with UUID d18df34531523330943317269bed7efc in dSYM: /Users/rollycervantes/Library/Caches/Xamarin/mtbs/builds/....iOS/fa122e58969ea2d60fc542f077988172/bin/iPhone/Release/....iOS.app.dSYM�[0m
2> �[32mSuccessfully uploaded Crashlytics symbols�[0m
2>C:\Users\rcervantes.nuget\packages\xamarin.firebase.ios.crashlytics\3.14.0.3\buildTransitive\Xamarin.Firebase.iOS.Crashlytics.targets(76,3): warning MSB3098: "Exec" task received an invalid value for the "StdOutEncoding" parameter.
2>C:\Users\rcervantes.nuget\packages\xamarin.firebase.ios.crashlytics\3.14.0.3\buildTransitive\Xamarin.Firebase.iOS.Crashlytics.targets(76,3): warning MSB3098: "Exec" task received an invalid value for the "StdErrEncoding" parameter.

Is there a solution already for this problem?

@padmasrisekar
Copy link

@jonathanfontaine did you fixed this issue? How to upload the dsyms file for xamarin ios project in visual studio

@jonathanfontaine
Copy link
Author

@padmasrisekar Nope, still have obfuscated stacktraces in some cases...

@devWaleed
Copy link

devWaleed commented Nov 24, 2020

I found out that Crashlytics Dashboard takes some time to process DSYM files and if multiple developers are working, all of them need to generate a release build and make sure DSYM symbols files are published as well which they will see in the console.

If any one of the develop doesn't create a release build then this error may still persist for long time.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants