You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
However, Crashlytics seems to still look for GoogleService-Info.plist in the project root when it tries to run upload-symbols script for the dSyms. This results in a build error.
I have tried to initialize Crashlytics with both Crashlytics.Configure() and Fabric.With(). The error persists.
Is there any way to configure Xamarin.Firebase.iOS.Crashlytics to accept a different path to GoogleService-Info.plist?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In
AppDelegate.cs
, I specify the path to the GoogleService-Info.plist file as part ofFirebaseOptions
:However, Crashlytics seems to still look for
GoogleService-Info.plist
in the project root when it tries to runupload-symbols
script for the dSyms. This results in a build error.I have tried to initialize Crashlytics with both
Crashlytics.Configure()
andFabric.With()
. The error persists.Is there any way to configure
Xamarin.Firebase.iOS.Crashlytics
to accept a different path toGoogleService-Info.plist
?The text was updated successfully, but these errors were encountered: