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
[severity:It's more difficult to complete my work]
I am experiencing an issue where crash logs are not being generated in my .NET 8.0 MAUI iOS application. I am using the latest version of Xamarin.Firebase.iOS.Crashlytics (8.10.0.3) for Firebase Crash Analytics. Despite implementing the setup as documented, crashes are not being reported to Firebase.
Steps to Reproduce:
1.Create a new .NET MAUI project targeting iOS.
2.Add the Xamarin.Firebase.iOS.Crashlytics NuGet package (v8.10.0.3).
3.Implement Firebase Crashlytics initialization in MauiProgram.cs as shown above.
4.Trigger a crash in the app using:
Firebase.Crashlytics.Crashlytics.SharedInstance.Log("Testing crash.");
throw new Exception("Test crash");
Observe that no crash logs appear in the Firebase Console.
Expected Behavior:
Crash logs should appear in the Firebase Console after the app crashes.
Additional Information:
The issue occurs only on iOS; Android appears to function correctly.
No error or warning logs related to Firebase Crashlytics are observed in the app output.
Request:
I would appreciate guidance on resolving this issue or confirmation if it is a known problem with .NET 8.0 or the Xamarin.Firebase.iOS.Crashlytics library.
Thank you for your assistance.
Original Comments
Feedback Bot on 1/16/2025, 09:39 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
The text was updated successfully, but these errors were encountered:
Hi @vsfeedback. We have added the "need-repro" label to this issue, which indicates that we require steps and sample code to reproduce the issue before we can take further action. Please try to create a minimal sample project/solution or code samples which reproduce the issue, ideally as a GitHub repo that we can clone. See more details about creating repros here: https://github.com/xamarin/xamarin-macios/blob/main/docs/bug-repro.md
This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.
Hi @vsfeedback. Due to inactivity, we will be closing this issue. Please feel free to re-open this issue if the issue persists. For enhanced visibility, if over 7 days have passed, please open a new issue and link this issue there. Thank you.
This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work]
I am experiencing an issue where crash logs are not being generated in my .NET 8.0 MAUI iOS application. I am using the latest version of Xamarin.Firebase.iOS.Crashlytics (8.10.0.3) for Firebase Crash Analytics. Despite implementing the setup as documented, crashes are not being reported to Firebase.
Environment Details:
MAUI Configuration: Below is the code used to register Firebase services in MauiProgram.cs:
Steps to Reproduce:
1.Create a new .NET MAUI project targeting iOS.
2.Add the Xamarin.Firebase.iOS.Crashlytics NuGet package (v8.10.0.3).
3.Implement Firebase Crashlytics initialization in MauiProgram.cs as shown above.
4.Trigger a crash in the app using:
Expected Behavior:
Crash logs should appear in the Firebase Console after the app crashes.
Additional Information:
The issue occurs only on iOS; Android appears to function correctly.
No error or warning logs related to Firebase Crashlytics are observed in the app output.
Request:
I would appreciate guidance on resolving this issue or confirmation if it is a known problem with .NET 8.0 or the Xamarin.Firebase.iOS.Crashlytics library.
Thank you for your assistance.
Original Comments
Feedback Bot on 1/16/2025, 09:39 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
The text was updated successfully, but these errors were encountered: