What problem does it solve?
Diagnosing .NET runtime failures on Apple mobile and Android platforms is difficult because failures surface as provisioning errors, emulator boot timeouts, code signing issues, and platform-specific code paths that never appear on desktop. This Skill provides the domain knowledge to classify failures as infrastructure or code, locate the right code paths, and fix them.
Core Features & Use Cases
- Failure Triage: Classify runtime-extra-platforms CI failures as infrastructure or code, with concrete indicators for each and guidance on reporting to tracking issues.
- Code Path Mapping: Map failure symptoms (build/packaging, test, NativeAOT, native interop, pipeline YAML) to exact files like AppleAppBuilder, AndroidAppBuilder, and eng/testing targets.
- Platform Gotchas: Document known traps such as Apple's six OS variants, dsymutil writing errors to stdout, Android's four architectures, and MSBuild evaluation order with NativeAOT.
- Use Case: A PR fails on
iossimulator-arm64 with a code signing error. Use this Skill to identify it as an infrastructure provisioning issue, check the pipeline YAML for the correct DevTeamProvisioning value, and report it on the tracking issue.
Quick Start
Triage the failing iossimulator-arm64 job in the runtime-extra-platforms pipeline and determine whether it is an infrastructure or code failure.