Skip to content
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

Bump Mono #4725

Merged
merged 1 commit into from
May 27, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .external
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
xamarin/monodroid:master@e795bcef375bc77da0bbe995fc9e57560ed5ddc0
mono/mono:2020-02@075c3f06197e3b969f4234d0f56a2e10ee6ee305
mono/mono:2020-02@8c085a99b32e99ae2f0a6b3de61541fefb4d3389
9 changes: 9 additions & 0 deletions Documentation/release-notes/4725.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
#### Application Mono Framework behavior on device and emulator

- [GitHub 4713](https://github.com/xamarin/xamarin-android/issues/4713):
Starting in Xamarin.Android 10.3, SIGSEGV during
`monodroid_typemap_java_to_managed` could cause apps to abort if the
application was built with the `$(AndroidEnablePreloadAssemblies)`
set to `False`, that is assembly preload at application startup
would be turned off and the application happened to use a managed
type which resides in an assembly not yet loaded by the runtime.