#4018 - Safety calls to/from Android Native Serialization

[aritchie]

Resolve #4018

Was unable to reproduce the issue, but the issue reported was clear to show where the problem existed. One user had reported coming from v4 to v5. I wonder if there was some old reports that weren't versioned properly?

• Safety all of the native serialization to & from dotnet
• Ensure ToDictionary call in serialization mechanism checks if the value can be pulled as a raw string from json
• End-to-end tests for (de)serializing native android SentryEvents
• Only enable the Android callback if SuppressSegfault is true OR native EnableBeforeSend is true OR BeforeSend options callback is NOT null

[albyrock87]

We're planning on releasing a new version on Monday, are you going to release a 5.2.1 today or on Monday with this fix?
I'm basically asking for ETA to better plan our next release.
Thanks! :)

[aritchie]

@albyrock87 5.3.0 is releasing today