MAUI / Android / Memory Optimizations #38043
Replies: 4 comments 6 replies
|
What are others doing, or what resources can I look at to move the needle and not get removed from the Playstore.: |
|
A have a similar problem. Google Play started to show the following warning for my MAUI app: The deadline is February 2027. There is also a link to R8 after this warning (https://developer.android.com/topic/performance/app-optimization/enable-app-optimization). I thought that I have R8 enabled, because the option was present in csproj file. However, turned out it's been actually disabled when I opened the project Properties dialog. The reason was that VS Studio somehow created two |
|
It seems that R8 isn't applied to MAUI apps correctly. I enabled R8 in the settings and reuploaded the updated version of the app to Google Play. However, it shows the same warning. Even worse, optimization level is now 0% instead of previous 1%. App bundle details page shows no "Shrinking percentage" and "R8 configuration" is also missing on Google Play. Also, aab size is about the same as in the previous version without R8. It seems there is a bug in MAUI and R8 isn't used at all, which will be problem in a few months when Google will start to enforce the new policy. |
Where i can find this warning? Is it only available when i publish a new version? Here are more infos: dotnet/android#12535 |
|
@AlleSchonWeg Google started to show this warning on several places in Google Play Console. The easiest way to check if a particular aab package is affected is to navigate to the list of releases and bundles (Test and release / Latest releases and bundles). Then in the list of bundles (under Latest app bundles), select the particular version and click on a arrow next to it for more detail. This shows a page with the most details, in case of a MAUI app: This way, you can see the warning also for versions published only in internal testing without a need to release them publicly. f the version with the problem is also in production, you'll see another strong warning in "Test and release / Production", or at the bottom of "Monitor and improve" page. Then, another message in "Monitor and improve / Android vitals / Overview" warning about bad behavior. Basically, it's very hard to overlook it now. Google is also preparing new insight tools for Google Play Console (https://android-developers.googleblog.com/2026/08/app-quality-memory-optimization-secure-onboarding.html). |
|
Thanks. I have no message. My app dex files are below 10mb. So I am not affected. |
|
Same Problem here: I've implement r8, EnableLLVM, etc. Then I went further based on the fact that r8 doesn't actually do anything for MAUI and added ArmDot for obfuscation as something else I found only but that was a waste of time since I got: so it's apparently something I'd have to purchase but won't do the job anyways. I'm getting a bit annoyed here... |
|
I think this issue is almost fixed in dotnet/android#12535 |
|
Forcing everyone to go to an extremely new Dot Net release might be a non-starter for people. Issues with .Net 10, Xcode building, and our paid for commercial 3rd party references caused no end of troubles from November till the end of January. I sincerely do not want to repeat that horror show a second time. Add to it, the Azure VM team dropping versions of required Xcode and Simulators from the standard builds. lord.
From: 김유석(Yu Seok Kim) ***@***.***>
Date: Tuesday, September 15, 2026 at 8:47 PM
To: dotnet/maui ***@***.***>
Cc: David Schlabach ***@***.***>; Author ***@***.***>
Subject: Re: [dotnet/maui] MAUI / Android / Memory Optimizations (Discussion #38043)
I think this issue is almost fixed in dotnet/android#12535<dotnet/android#12535>
this works maybe final fix soon or at least fix in .NET 11 GA
—
Reply to this email directly, view it on GitHub<#38043?email_source=notifications&email_token=A6M2G4CEBBCHFS6TTOSQKW35PHPLFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGU3TGNZZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18457379>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A6M2G4GPTWOHVYFWDJBINT35PHPLFAVCNFSNUABIKJSXA33TNF2G64TZHMZDMMRTHE2TEMRUHNCGS43DOVZXG2LPNY5TCMBXGIZDQMRTUF3AE>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/A6M2G4EPBICFHHVGR2ZDCV35PHPLFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGU3TGNZZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android<https://github.com/notifications/mobile/android/A6M2G4DGERZWGLOWKWL4YRL5PHPLFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGU3TGNZZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today!
You are receiving this because you authored the thread.
CAUTION! - External Message
|
|
I think so, I also hope At least .NET MAUI team will do patch backport into .NET 10, when they success on .NET 11 I saw current .NET 10 SDK included R8 didn't export correct r8 optimized information that recognized on Play Store console I think, .NET MAUI's working to fix going well This issue has very important impacts, but I trust will be fix at least not lately |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We were notified that soon because of the Memory pricing issue, Google is going to crack down on apps it doesn't consider optimized.
We have the following set for releases
Google is only doing a statically analysis and says our app is "low optimized" with no obfuscation.
For resources our app has 1.5 megs of images and 800k of fonts, the rest is MAUI code. What are others doing, or what resources can I look at to move the needle and not get removed from the Playstore. Performance wise, even on a simulator the app is fast and our users haven't complained. However, Google is basically saying come early next year, they are gonna start delisting apps they don't find performant based on their analysis tool.
All reactions