-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
.NET 8 Preview 6 Android crashes with System.MissingMethodException #16166
Comments
To my knowledge, we did not hit any similar problems when .NET 7 moved to API 33 by default. What are the |
Hi @Syed-RI. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
@jonathanpeppers and @jsuarezruiz added repro and relevant logs. Hope that helps? |
@Syed-RI yes, this looks like an API change in MAUI:
This isn't anything to do with Android API 34? The API was changed because the old one could introduce memory leaks: #15303 |
@jonathanpeppers Thanks for confirming, but it does breaks the libraries that relies on this right? How to get around this? |
@PureWeen @hartez @mattleibow do we have a recommendation for API changes like this? From what I see, the owner of this library would need to build a preview NuGet package for .NET 8? |
@jonathanpeppers @jsuarezruiz @PureWeen @mattleibow Hmm more importantly, I think breaking public API changes like this should be handled more gracefully internally at MAUI project. Maybe mark the existing method as |
I don't know how "public" handler APIs are? It might be they have a less strict policy, compared to an API change on |
Me neither and that was just my assumption as I have not done much due diligence to check the PR referenced above and the source for the library. Apologies |
* Reinstate IContentView and ILayout methods Fixes #16166 * Limit fake methods to NET Standard 2.0 * Reverse the polarity * Simplify * Work around compatibility implementations of ICV/ICPL methods on ScrollView * Use correct interface for Frame
Wow that was quick!. Thanks everyone! ❤️ |
* [create-pull-request] automated change (#16413) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * [Windows] Fix Border corners clipping issue (#14403) * Fix Border corners clipping mistake on Windows * Updated impl * Created method to avoid duplicated code * Revert uneccesary changes * Changes in clipping sizing * Fix Rui issue * Added device tests * Remove unnecessary changes --------- Co-authored-by: Javier Suárez <[email protected]> * Add ViewHandler Mapper docs (#16296) Co-authored-by: Juan Diego Herrera <[email protected]> * [create-pull-request] automated change (#16427) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Fix device tests to tun on arm64 (#16408) * Build on arm64 * magic * Only install on Arm64 machines * cleanup demands on the pipeline and add windows parameter * Print system arch * Fix getting OSArchitecture --------- Co-authored-by: Rui Marinho <[email protected]> * [uitests] Fix appium script (#16451) * Bump node version * Add more info to install script * Try clean modules before install * Uninstall before install * fix * Cleanup yaml * Write output of drivers * Try remove plugins before uninstall * [iOS] Fix Editor placeholder issues (#15883) * Fix iOS Editor placeholder size, characterspacing and fontsize issues * Added Device Test * Invalidate CharacterSpacing updating the placeholder * Updated Impl * [Essentials] Make PublisherName public on NET8 (#16454) * Fix EntryCellRenderer to use fromhandler for text changes (#16458) * [compatibility] Skip test on iOS (#16452) * [iOS] Re-enable editor tests (#16365) * Re-enable editor tests on iOS * Fix merge problem * [build] Remove the old step for vs insertion on release (#16457) * Reinstate IContentView and ILayout methods (#16411) * Reinstate IContentView and ILayout methods Fixes #16166 * Limit fake methods to NET Standard 2.0 * Reverse the polarity * Simplify * Work around compatibility implementations of ICV/ICPL methods on ScrollView * Use correct interface for Frame * [net8.0] Don't move to use arm yet here * [net8.0] Make UpdateBackground public (#16453) * [api] Make UpdateBackground public * Keep extensions internal * Fix issue setting ContentPage gradient background on iOS/Catalyst (#15832) * Fix provisioning script * [provisioning] Set Xcode path correctly for Xamarin Hosting --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Javier Suárez <[email protected]> Co-authored-by: Javier Suárez <[email protected]> Co-authored-by: Matthew Leibowitz <[email protected]> Co-authored-by: Juan Diego Herrera <[email protected]> Co-authored-by: Shane Neuville <[email protected]> Co-authored-by: E.Z. Hart <[email protected]>
Description
It appears by default, .NET 8 P6 is targeting Android api 34 which breaks quite a few 3rd party libraries (https://github.com/sswi/AcrylicView.MAUI/tree/master , https://github.com/syncfusion/maui-demos for example) who are yet to target .NET 8 and Android 34. Im seeing various exception such as, class not found exception.
Is there a way to lower the Android target in .NET8 P6 or we are forced to wait while Android 34 gos GA, then library authors update their library and then we, the MAUI mortals get to taste .NET 8 ?
Steps to Reproduce
N/A
Link to public reproduction project repository
Repro attached:
Preview6.zip
Build and deploy to an emulator running on API 29 (same goes for emulator running on API 34).
Log for Acrylic library:
log.txt
Log for Sf library:
log2.txt
Version with bug
8.0.0-preview.6.8686
Last version that worked well
7.0.52
Affected platforms
Android
Affected platform versions
Android 34
Did you find any workaround?
NOPE
Relevant log output
For Acrylic library I see:
For SF library I see:
The text was updated successfully, but these errors were encountered: