Area: Android Resources

Issues with Android Resources (aapt, etc)

Area: App+Library Build

Issues when building Library projects or Application projects.

Area: App Runtime

Issues in `libmonodroid.so`.

Issues in Java Library Binding projects.

Area: Commercial

Issues with non-OSS components.

Issues using or interacting with the debugger.

Area: Design-Time Build

Issues with VS design-time build.

Area: Documentation

Issues with documentation.

Issues with F# (fsharp) projects

Issues with sockets / HttpClient.

Area: Installer

Issues with macOS .pkg or Windows .vsix contents.

Issues when linking assemblies.

Area: Mono.Android

Issues with the Android API binding (Mono.Android.dll).

Area: Mono Runtime

Mono-related issues: BCL bugs, AOT issues, etc.

Area: Performance

Issues with performance.

Area: Templates

Issues with templates shipped with the Android workload.

Area: Unit Tests

Issues with repo unit tests.

Area: xamarin-android Build

Issues building the xamarin-android repo *itself*.

Component does not function as intended.

Pull requests that update a dependency file.

PR should not be merged.

Proposed change to current functionality.

full-mono-integration-build

For PRs; run a full build (~6-10h for mono bumps), not the faster PR subset (~2h for mono bumps)

good-first-issue

Issues that are great for first contributors

Pull requests that update Java code

A xamarin-android contributor needs to review

Issues that need more information from the author.

Issues that need to be assigned.

Issues that are potentially no longer relevant.

Pull requests that update Submodules code

Upstream Android

Issue exists in the upstream Android OS/API/SDK

use-merge-commit

Normally we squash-and-merge PRs. Use this label so we instead use a merge commit.

use-rebase-and-merge

Normally we squash-and-merge PRs. Use this label so we instead rebase & merge.

For internal use only; creates a VSTS "mirror" issue.

No labels found. Sorry about that.