Skip to content

Conversation

@jamescrosswell
Copy link
Collaborator

@jamescrosswell jamescrosswell marked this pull request as ready for review August 21, 2025 10:12
/// <param name="message">The message string to write.</param>
/// <param name="args">Arguments for the formatted message string.</param>
public delegate void DebugLogger(string message, params object?[] args);
public delegate void DebugLogger(DebugLoggerLevel level, string message, params object?[] args);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: breaking change

Since we don't mention Sentry.Android.AssemblyReader in the README as a top-level package,
nor in our documentation as a platform guide,
we do not consider changes to the public surface area of this Assembly a breaking change,
since it's main purpose is to be consumed by the Android TFMs of Sentry,
right?

Copy link
Collaborator Author

@jamescrosswell jamescrosswell Aug 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, actually it's only used from here:

/// <summary>
/// Allows integrations to provide a custom assembly reader.
/// </summary>
/// <remarks>
/// This is for Sentry use only, and can change without a major version bump.
/// </remarks>
#if !__MOBILE__
[CLSCompliant(false)]
#endif
[EditorBrowsable(EditorBrowsableState.Never)]
public Func<string, PEReader?>? AssemblyReader { get; set; }

It looks like Matt added that comment in #2127

@bruno-garcia given that sentry-xamarin is no longer being maintained, could we potentially move the AssemblyReader back into the main Sentry packages and make all this stuff internal again (not in this PR of course - probably for v6.0)?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm in favor of that, just get rid of that package and make our lifes easier

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to be fair, it should never have been created. It's very little code and only used in 2 package we own. We could have copy pasted things and manually keeped them in sync.

We knew Xamarin was schedule for retirement by then already.

Classic .NET overengineering

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jamescrosswell jamescrosswell merged commit b3e91ab into main Aug 25, 2025
33 checks passed
@jamescrosswell jamescrosswell deleted the assembly-reader-logger branch August 25, 2025 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Refactor AssemblyReaders to allow different logging levels

4 participants