Page needs updating for .NET 10
- Dominant language
- No language data
- Stars
- 282
- Forks
- 265
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
### Type of issue
Outdated article
### Description
The page at https://learn.microsoft.com/en-gb/dotnet/maui/android/deployment/publish-ad-hoc?view=net-maui-10.0 needs to be updated as the stated method for publishing an Android app no longer functions in the way described.
I have done a great deal of investigation and the method that works for .apk files is as follows:
1. Follow the instructions in the article "Publish an Android app using the command line" to create a keystore.
2. Using the steps described in the section "Define build properties in your project file" to create a PropertyGroup in the project file for the keystore values.
3. Now select Publish from the drop-down menu for the application. This will launch the Archive Manager.
4. Provided that the keystore settings in the PropertyGroup are correct, the app will complete the build and sign the android .apk file.
5. Correct signing can be confirmed by running _jarsigner_ on the command line. Navigate to the _bin\Release\net10.0-android_ folder and run jarsigner against the .apk file. For example _jarsigner -verify com.companyname.mymauiapp.apk_. The output should contain _Jar verified_ for a correctly signed file.
### Page URL
https://learn.microsoft.com/en-gb/dotnet/maui/android/deployment/publish-ad-hoc?view=net-maui-10.0
### Content source URL
https://github.com/dotnet/docs-maui/blob/main/docs/android/deployment/publish-ad-hoc.md
### Document Version Independent Id
b66ab819-b8b5-6f50-186d-886a0fb7e25c
### Platform Id
1c05ef10-9451-929d-a1f3-09acae9f6907
### Article author
@davidortinau
### Metadata
* ID: b66ab819-b8b5-6f50-186d-886a0fb7e25c
* PlatformId: 1c05ef10-9451-929d-a1f3-09acae9f6907
* Service: **dotnet-mobile**
* Sub-service: **dotnet-maui**
Contributor guide
Assessment
This issue has not been assessed yet.