0

I have a Maui Blazor Hybrid app, it runs on .net7.0 with target framework API 33 android 13. Since I have changed this I cant sign my android app. I can create my keystore file successfully, but as soon as I try and select the file to use, it disappears from the file upload box in the image below.

Package Sign section

I have tried numerous times to re-create the keystore file, I checked the rights on the file, I have updated, uninstalled and reinstalled visual studio. Normal Android .net 7.0 work fine just on .net7.0-adroid33.0

Improve this question
4
  • " Normal Android .net 7.0 work fine just on .net7.0-adroid33.0 " You mean if it's .net7.0-adroid33.0, the app will not work fine? Commented Jan 19, 2024 at 5:52
  • @JianweiSun-MSFT yes as soos as I change the TargetFramework for android in the property settings to Android 13 API 33, it wont allow me to upload my keystore file when i try and do the package signing. Commented Jan 19, 2024 at 6:47
  • You mean you want this effect? Commented Jan 19, 2024 at 8:02
  • 1
    Hi everyone, I got another way to sign which resolved the issue, I unchecked the sign package in the Android options section, then once the archive is created I click on distribute and can then successfully create the signature and signage of the package. Commented Feb 5, 2024 at 7:48

1 Answer 1

Reset to default
0

Well, according to your comment, as an answer:

I unchecked the sign package in the Android options section, then once the archive is created I click on distribute and can then successfully create the signature and signage of the package.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.