Skip to content

[android][infra] Validate .NET 11 Android functionality across different API versions #122021

Closed

Description

@matouskozak

Why

Android versions come with broad range of different API versions. Currently, most of our testing uses only API 29 (e.g. Android emulators Ubuntu.2204.Amd64.Android.29.Open). However, in .NET 11, we support API levels 21(?) and higher. We should periodically test functionality on different API versions.

How

Description of how the testing is done, can be found in #107868. Previous test run e.g., #120093. In addition, to testing Mono Android scenarios, we should also include CoreCLR in this testing.

What

This verification makes the most sense to be done on the pre-release branch of dotnet/runtime. Optionally, we can also verify servicing branches if we await any issues. Throughout the release cycle, this validation should be performed periodically to prevent unexpected issues caused by un-tested API levels.

This verification should be performed periodically throughout the Preview and RC release cycle, an example of verification schedule:

  • Preview 1
  • Preview 4
  • Preview 5
  • Preview 7
  • RC2

Activity

  1. added this to the 11.0.0 milestone on Nov 27, 2025
  2. dotnet-policy-service commented on Nov 27, 2025

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'arch-android': @vitek-karas, @simonrozsival, @steveisok, @akoeplinger
    See info in area-owners.md if you want to be subscribed.

  3. dotnet-policy-service commented on Nov 27, 2025

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @akoeplinger, @matouskozak, @simonrozsival
    See info in area-owners.md if you want to be subscribed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions