-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for native iOS and Android symbolication support for the .NET provider (.net-Android, .net-iOS) #532
Comments
Thank you for your suggestion regarding adding support for native iOS and Android symbolication in Raygun4Net.NetCore. We appreciate your input and are taking a look into possibly implementing this. To better understand the necessity and context of this request, could you provide specific examples where symbolication is required? This would help us assess the impact and prioritize this feature accordingly. In many cases, marshaled exceptions tend to be lower-level exceptions that may not directly relate to the code you have written. For instance, on Android, you might encounter exceptions like FileNotFoundException that are more related to system-level operations rather than application-level logic. In the above case, symbolication isn't required. Could you share any examples where you do need this, one case where this might be required is when a binding library causes errors but I'd like to know what specific use case you have for this. |
To understand, Would symbolication be helpful in understanding errors like these? this ios this android this android this android |
Thank you for sharing the details of this issue. We will need to conduct further investigation to determine what can be done in this area. At this moment, we don't have immediate plans to address this, but we will update this thread if it becomes a priority in the future. Symbolication of native stack traces can sometimes be useful, particularly in cases where errors originate from native components or third-party libraries. However, in MAUI or .NET Native apps, since the code is written in C# and runs on the Mono runtime, native exceptions generally have less impact on debugging compared to managed exceptions. We appreciate your input and encourage you to share specific examples where symbolication has been or could be helpful. This will assist us in assessing the impact and prioritizing this feature accordingly. |
Since Raygun handles the marshaling of native exceptions in .NET-Android and .NET-iOS, I would request that Raygun add support for native iOS and Android symbolication for the Raygun4Net.NetCore
The text was updated successfully, but these errors were encountered: