microsoft
Issue with localization of .NET exceptions
Description
Standard .NET exception messages are localized.
This is really annoying when it comes to crash reporting.
First of all, it can be difficult to identify issues.
For instance can you guess the following message?
개체 참조가 개체의 인스턴스로 설정되지 않았습니다
I don't... Actually, this is:
Object reference not set to an instance of an object.
It also breaks the grouping of exceptions in the AppCenter portal. Because they are grouped by message, two identical exceptions (with the same stack trace) will appear as different exceptions, simply because users have a different language setup.
This basically renders exceptions grouping useless...
Is there a way with the AppCenter Crashes SDK to report exceptions in English only?
Details
- What is your app platform (Xamarin.Android or Xamarin.iOS or UWP)?
- WPF
- If using Xamarin.Forms or if using portable/shared code to call our SDK APIs, are you using shared project, PCL code or .NET standard code for the application? Which .NET standard version or which PCL profile?
- N/A
- Which SDK version are you using?
- 2.4.0-preview
- Which OS version did you experience the issue on?
- Windows 10
- What device version did you see this error on? Were you using an emulator or a physical device?
- N/A
- What third party libraries are you using?
- N/A
- Please enable verbose logging for your app using
AppCenter.LogLevel = LogLevel.Verbosebefore your call toAppCenter.Start(...)and include the logs here:
Hey! 😄Yeah, that must be really annoying. Thank you for the request, we'll see what we can do.
Moving this to a central appcenter repository where we are tracking/prioritizing all requests. Thanks
I'm surprised this issue isn't seeing more action. As far as I'm concerned it is a major problem for the reasons already described.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
Bumping... BTW marking issues as stale, just because no one has any updates doesn't mean it is not important anymore.
Hi @ricardoboss and @macmade ,
Exception localization is handled by dotnet based on the language preferences of the end user. They still have an open issue here: https://github.com/dotnet/runtime/issues/46656. There are some workarounds with switching to eng locale while saving a crash report, however I don't think it is a good idea to use such a hack in SDK.
I personally don't see any "normal" way to fix the issue at this moment, but let me know if you have any ideas. I'm moving this feature request to the appcenter-sdk-dotnet repo.
At least this issue did not get closed yet... They closed mine in favor of this one which now is closed again in favor of another...
As we do not have plans to add support for this feature in the next year, I'm closing the issue.
Just like that... Here's another one that isn't closed yet...: https://github.com/dotnet/runtime/issues/40427