osu-lazer/osu.Android/AndroidManifest.xml

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="sh.ppy.osulazer" android:installLocation="auto">
	<uses-sdk android:minSdkVersion="21" android:targetSdkVersion="33" />
	<application android:allowBackup="true"
				 android:supportsRtl="true"
				 android:label="osu!"
				 android:icon="@mipmap/ic_launcher"
				 android:roundIcon="@mipmap/ic_launcher" />
	<!-- for editor usage -->
	<uses-permission android:name="android.permission.READ_MEDIA_IMAGES" />
	<uses-permission android:name="android.permission.READ_MEDIA_AUDIO" />
	<!--
		READ_MEDIA_* permissions are available only on API 33 or greater. Devices with older android versions
		don't understand the new permissions, so request the old READ_EXTERNAL_STORAGE permission to get storage access.
		Since the old permission has no effect on >= API 33, don't request it.

		Care needs to be taken to ensure runtime permission checks target the correct permission for the API level.
	-->
	<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" android:maxSdkVersion="32"/>
</manifest>
-												Add Android project

											
										
										
											2018-12-13 14:10:15 +08:00
+								<?xml version="1.0" encoding="utf-8"?>
-												Adjust Android package versioning to .NET 6

With .NET 6, the way Xamarin package versioning works has changed.

- The `ApplicationVersion` MSBuild property aims to replace
  `android:versionCode` in the manifest.
- The `ApplicationDisplayVersion` MSBuild property aims to replace
  `android:versionName` in the manifest.

More about this can be read in Xamarin docs:

    https://github.com/xamarin/xamarin-android/blob/ec712da8c1ce03f71578e08cafb6a767cdb90cd5/Documentation/guides/OneDotNetSingleProject.md

To this end:

- Manual `version{Code,Name}` specs are removed from
  `AndroidManifest.xml`, as they were preventing MSBuild properties
  from functioning properly.
- `Version` now defaults to 0.0.0, so that local builds don't appear
  like they were deployed (see `OsuGameBase.IsDeployedBuild`).
- `ApplicationDisplayVersion` now defaults to `Version`.
  This addresses the Android portion of #21498.
- `ApplicationVersion` can now be specified by command line,
  but still needs to be supplied manually for version detection to
  work correctly. See `OsuGameAndroid.AssemblyVersion` for more info.

Putting the pieces together, the complete publish command to deploy
a new build should look something like so:

    dotnet publish -f net6.0-android \
                   -r android-arm64 \
                   -c Release \
                   -p:Version=2022.1228.0 \
                   -p:ApplicationVersion=202212280

											
										
										
											2022-12-28 17:36:54 +08:00
+								<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="sh.ppy.osulazer" android:installLocation="auto">
-												Bump Android target SDK version to 33

											
										
										
											2023-08-21 05:36:07 +08:00
+									<uses-sdk android:minSdkVersion="21" android:targetSdkVersion="33" />
-												Update android icons

											
										
										
											2024-01-27 02:02:44 +08:00
+									<application android:allowBackup="true"
 												 android:supportsRtl="true"
 												 android:label="osu!"
 												 android:icon="@mipmap/ic_launcher"
 												 android:roundIcon="@mipmap/ic_launcher" />
-												Declare media permissions in game project for editor usage

											
										
										
											2023-08-21 05:37:11 +08:00
+									<!-- for editor usage -->
 									<uses-permission android:name="android.permission.READ_MEDIA_IMAGES" />
 									<uses-permission android:name="android.permission.READ_MEDIA_AUDIO" />
-												Add inline comment matching framework

											
										
										
											2023-12-04 11:10:31 +08:00
+									<!--
 										READ_MEDIA_* permissions are available only on API 33 or greater. Devices with older android versions
 										don't understand the new permissions, so request the old READ_EXTERNAL_STORAGE permission to get storage access.
 										Since the old permission has no effect on >= API 33, don't request it.
 										Care needs to be taken to ensure runtime permission checks target the correct permission for the API level.
 									-->
-												Request `READ_EXTERNAL_STORAGE` on older android versions

											
										
										
											2023-12-01 20:00:34 +08:00
+									<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" android:maxSdkVersion="32"/>
-												Add inline comment matching framework

											
										
										
											2023-12-04 11:10:31 +08:00
+								</manifest>