Issues AMM0000 error in the AndroidManifest
See original GitHub issueDescription
I get errors from PlayStore trying to upload my *-signed.aab file. (after following Jerald Versluis instructions on https://www.youtube.com/watch?v=jfSVb_RR7X0) I get an error: You uploaded an APK or Android App Bundle that was signed in debug mode. You need to sign your APK or Android App Bundle in release mode After researching solutions to this problem, it appears that the configurations for debugging aren’t always consistently followed, so on a mission, I set out to disable any remnants that sound at all related to debugging. I edited the project file and set: 1. Build -> General -> Debug symbols from: PDB file, portable across platforms to: No Symbols are emitted 2. Developer instrumentation I unchecked the option for “Debug” (now it is empty/false) 3. iOS-> Debug -> Debugging changed from True to False
Now when I do only the build of release mode (not the Publish which signs the *.aab), I get this error: Severity Code Description Project File Line Suppression State Error AMM0000 uses-sdk:minSdkVersion 19 cannot be smaller than version 21 declared in library C:\MTRClient\MTRClient\obj\Release\net6.0-android\lp\130\jl\AndroidManifest.xml as the library might be using APIs not available in 19 Suggestion: use a compatible library with a minSdk of at most 19, or increase this project’s minSdk version to at least 21, or use tools:overrideLibrary=“androidx.security” to force usage (may lead to runtime failures) MTRClient C:\MTRClient\MTRClient\obj\Release\net6.0-android\AndroidManifest.xml 28
so… I can’t upload because of debug mode, and I can’t turn off debug mode. Quite difficult to publish to the Google Play store…
Steps to Reproduce
Change debugging settings in Project file as explained above.
Link to public reproduction project repository
no
Version with bug
6.0.486 (current)
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
android
Did you find any workaround?
Not even after spending several hours was I able to find a way to publish my app to the Google Play store.
Relevant log output
no
Issue Analytics
- State:
- Created 10 months ago
- Reactions:1
- Comments:10 (1 by maintainers)

Top Related StackOverflow Question
@tradegear that comment is not productive, and does not adhere to our Code of Conduct. Please read the policy and conduct your interactions accordingly in the future.
The error looks like you could have a couple of potential issues:
android:debuggable="true"set in your final build. I believe we disable this by default in the Android build targets when you use the build configurationRelease. I’d suggest building withdotnet build -f net7.0-android -c Release MyApp.csprojand inspecting the resulting .apk file’s manifest to confirm.Yes we ask for repro samples, because it’s one of the best ways for us to quickly analyze an issue and plan for how to fix and prioritize it in the future. Help us help you by narrowing down reproductions of your issues. We are doing our best to priortize issues that have the biggest impact across the community with the time and resources we have. If we can’t easily reproduce a problem, and we don’t have a good idea that many people are experiencing it as well, we are less likely to be able to confirm it, and prioritize fixing it.
Hello lovely human, thank you for your comment on this issue. Because this issue has been closed for a period of time, please strongly consider opening a new issue linking to this issue instead to ensure better visibility of your comment. Thank you!