You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i enable AOT and Trim in my project i run into this error. Disabling both options let the app run as intended. All projects inside the solution are on .net8 and bin/obj folders have been deleted to force rebuild. How do i fix this?
Steps to Reproduce
No response
Link to public reproduction project repository
No response
Version with bug
8.0.7 SR2
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
no
Relevant log output
'Could not resolve type with token 01000005 from typeref (expected class 'System.Runtime.CompilerServices.InternalsVisibleToAttribute' in assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51')'
The text was updated successfully, but these errors were encountered:
The short answer is that MAUI (The UI Framework) is currently not NativeAOT friendly. It's being tracked for .NET 9. Currently, AFAIK, the only platform that could "fully" support compiling with NativeAOT would be Apple platforms (iOS/Mac Catalyst, etc). WinUI doesn't support NativeAOT and Android currently supports it for native code, but with no Java interop.
Description
When i enable AOT and Trim in my project i run into this error. Disabling both options let the app run as intended. All projects inside the solution are on .net8 and bin/obj folders have been deleted to force rebuild. How do i fix this?
Steps to Reproduce
No response
Link to public reproduction project repository
No response
Version with bug
8.0.7 SR2
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
no
Relevant log output
The text was updated successfully, but these errors were encountered: