question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issues AMM0000 error in the AndroidManifest

See original GitHub issue

Description

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:closed
  • Created 10 months ago
  • Reactions:1
  • Comments:10 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
Redthcommented, Nov 9, 2022

@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:

  1. Your android manifest has the 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 configuration Release. I’d suggest building with dotnet build -f net7.0-android -c Release MyApp.csproj and inspecting the resulting .apk file’s manifest to confirm.
  2. You may not be signing correctly. I’d suggest reviewing the documentation to create the appropriate keys.
  3. Unfortunately the “Debug symbols” in the project settings is slightly misleading as those refer to .NET managed debug settings, and do not directly influence the platform settings for debug options which is what Google cares about.

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.

0reactions
msftbot[bot]commented, Nov 27, 2022

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!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Is there a way to fix error: AMM0000 when I try to upgrade ...
I'm trying to upgrade the app to work on android 10 with visual studio /mac/. From SDK Manager -> I download Android SDK...
Read more >
Issues AMM0000 error in the AndroidManifest - dotnet/maui
Description. This error is coming from the generated Android Manifest for a sample app for a library I've been migrating to Maui from...
Read more >
AMM0000 android:exported needs to be explicitly specified ...
Hello,. It is caused by the incompatibility of the NuGet Package with Android 12. You could find the following tips by referring to...
Read more >
Xamarin.Android, AndroidManifest.xml ...
Common.targets(3,3): Error AMM0000: is also present at AndroidManifest.xml:14:9-41 ... This issue is showed into DEBUG and RELEASE mode!! Environment.
Read more >
AndroidX on VS2019 incompability with older API level
Common.targets(1813,3): error AMM0000: uses-sdk:minSdkVersion 23 ... obj\Debug\100\lp\6\jl\AndroidManifest.xml as the library might be using ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found