Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I believe this change would disable the hacky workaround for the lack of xcframework support in Unity, but don't understand why it was working for me in Unity 2021.3 because Unity claims that .xcframeworks are supported in Unity 2021.3, 2022.3 and Unity 6: https://discussions.unity.com/t/does-unity-support-xcframeworks/240687/5
xcframework generation and the workaround was introduced in Realm.NET 10.3: https://github.com/realm/realm-dotnet/pull/2475/files
but it was also mentioned since that xcframework is no longer generated and we are just dealing with a .framework in 10.19 and 20.1:
#2906 (comment)
So it seems that the workaround itself shouldn't be causing the issue, it's possible that this is just a Unity 6 compatibility issue.
I have no way to test this change without a packaged up tarball file of Realm for Unity because the suggested method had dependency issues I wasn't able to fix (Cecil.pdb, Cecil.Rocky etc)
I'd like to test this change in either Realm 10.19 or 20.1 in Unity 6 - could you provide a tarball with this change? Or provide instructions on how I can generate this myself?
Fixes #3693
TODO