Expose Android package output items

[Redth]

Why this change is necessary

Android package outputs are difficult for custom targets, CI workflows, and higher-level workloads to discover reliably. Final APK and AAB paths are calculated by the Android build, while dotnet publish previously rediscovered packages indirectly. Consumers therefore had to duplicate Android-specific naming and packaging logic.

This change exposes the authoritative final package outputs through @(ApplicationArtifact) and a callable GetApplicationArtifacts target. The item name is intentionally platform-neutral so workloads such as MAUI and other .NET mobile platforms can enrich or populate the same contract.

What changed

• Added @(ApplicationArtifact) collection after Android package, signing, and universal APK generation.
• Included unsigned and signed APK/AAB outputs, per-ABI APKs, and universal APKs when produced.
• Added Android-specific metadata:
  • PackageFormat: apk or aab
  • Signed: whether the package is signed
  • PackageId: the resolved Android package name
  • Abi: the ABI for per-ABI APKs
• Added GetApplicationArtifacts, which builds the project and returns @(ApplicationArtifact).
• Added $(GetApplicationArtifactsDependsOn) as an extension point that runs after Android creates the items, allowing later imports such as MAUI to add metadata before either GetApplicationArtifacts or Publish returns them.
• Updated Publish to:
  • use @(ApplicationArtifact) as the source of package entries in @(ResolvedFileToPublish);
  • copy those packages to $(PublishDir);
  • return @(ApplicationArtifact) with identities updated to the published paths while preserving metadata.
• Removed the publish-time existence filter so an expected artifact is not silently omitted from the returned item group if its publish copy is missing.
• Extended the test DotNetCLI helper to accept arbitrary MSBuild command-line arguments, including -getTargetResult.
• Documented @(ApplicationArtifact), GetApplicationArtifacts, the Publish return contract, metadata, extension behavior, and command-line query examples.

Tests

Added BuildTest.DotNetBuildReturnsApplicationArtifacts coverage for:

• Debug APK results returned by GetApplicationArtifacts.
• Debug APK publish paths returned by Publish.
• Release AAB results, including unsigned/signed AABs and the signed universal APK.
• A MAUI-style $(GetApplicationArtifactsDependsOn) extension that observes the Android-produced items and enriches their metadata before they are returned.

The tests parse MSBuild -getTargetResult JSON and validate artifact count, file name, package format, signed status, package ID, ABI, and extension-provided metadata.

Issues fixed

N/A

[Copilot]

Pull request overview

This PR makes Android packaging outputs discoverable by introducing a stable @(AndroidPackageOutput) item group (and a GetAndroidPackageOutputs target) so custom targets and CI workflows can consume authoritative APK/AAB paths without reimplementing packaging logic.

Changes:

• Add _CollectAndroidPackageOutputs + GetAndroidPackageOutputs, and wire collection into build/sign/package order so outputs are available after packaging/signing.
• Update dotnet publish flow to publish packages via @(AndroidPackageOutput) (instead of filename globs) and then rewrite the item group to point at $(PublishDir) copies.
• Add test coverage and documentation for the new item group.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/Xamarin.Android.Build.Tasks/Xamarin.Android.Common.targets	Adds package-output collection target and public target returning @(AndroidPackageOutput) with metadata.
src/Xamarin.Android.Build.Tasks/Microsoft.Android.Sdk/targets/Microsoft.Android.Sdk.BuildOrder.targets	Schedules _CollectAndroidPackageOutputs after package/sign/universal APK creation and in related target dependency chains.
src/Xamarin.Android.Build.Tasks/Microsoft.Android.Sdk/targets/Microsoft.Android.Sdk.Publish.targets	Publishes using @(AndroidPackageOutput) and updates items to the final publish paths after copy.
src/Xamarin.Android.Build.Tasks/Tests/Xamarin.Android.Build.Tests/XASdkTests.cs	Adds dotnet publish assertions ensuring package outputs flow into ResolvedFileToPublish and @(AndroidPackageOutput).
src/Xamarin.Android.Build.Tasks/Tests/Xamarin.Android.Build.Tests/PackagingTest.cs	Adds assertions that signed APK outputs (including per-ABI) appear in @(AndroidPackageOutput) with correct metadata.
Documentation/docs-mobile/building-apps/build-targets.md	Mentions @(AndroidPackageOutput) for SignAndroidPackage (needs a section for the new GetAndroidPackageOutputs target).
Documentation/docs-mobile/building-apps/build-items.md	Documents the new @(AndroidPackageOutput) item group and its metadata.

[Redth]

macios equivalent: dotnet/macios#25723

[jonathanpeppers]

/review

[github-actions]

✅ Android PR Reviewer completed successfully!

[github-actions]

🤖 Code Review — Expose Android package output items

Verdict: ⚠️ Needs Changes (minor)

Solid, well-scoped MSBuild change. The new @(ApplicationArtifact) item group and GetApplicationArtifacts / Publish return contract are clean, the metadata surface (PackageFormat, Signed, PackageId, Abi) is intentionally small, and the docs are thorough. I verified:

• ✅ PackageId="$(_AndroidPackage)" correctly maps to the resolved Android package name (ApplicationId), matching the docs.
• ✅ The aab;apk case is handled: _AndroidAdditionalPackageFormats=apk produces the signed universal APK at $(ApkFileSigned), which the unguarded Exists('$(ApkFileSigned)') include captures (3 items for AAB — matches the test).
• ✅ _CollectApplicationArtifacts is wired into all the build/sign/package dependency chains after signing runs.

Issues (2 inline)

1. ⚠️ MSBuild targets — _UpdateApplicationArtifactsForPublish silently drops any artifact not found in $(PublishDir) (Publish.targets).
2. 💡 Testing — Test comment references the wrong target name _CreateApplicationArtifacts (BuildTest.cs).

Notes (not blocking)

• PR description vs. diff: The description lists added coverage in XASdkTests.DotNetPublish and PackagingTest.CheckSignApk (Release aab;apk, @(ResolvedFileToPublish) flow, per-ABI signed APKs). Those files are not in this diff — only BuildTest.cs was changed. Please reconcile the description with the actual test coverage, or add the missing tests. The per-ABI (AndroidCreatePackagePerAbi=true) and aab;apk publish paths in particular are currently exercised only indirectly.
• CI has no completed statuses yet (pending) — verdict assumes the pipeline goes green.

Nice work on the documentation and the extension-hook ordering test.

Generated by Android PR Reviewer for #11674 · 140.5 AIC · ⌖ 13.1 AIC · ⊞ 6.8K
_{Comment /review to run again}