Add debug build configuration support for MAUI Android and iOS scenarios

[Copilot]

Adds support for debug configured runs (-c Debug) for MAUI Android and iOS scenario benchmarks by passing buildConfig: debug through the pipeline and into the pre.py publish command.

Changes

scripts/run_performance_job.py

• Added DEFAULT_BUILD_CONFIG constant for the default "Release" configuration
• Extended get_run_configurations() to include BuildConfig in configurations for maui_scenarios_android and maui_scenarios_ios run_kinds only when the build configuration is not the default (Release). This preserves existing trend data for Release builds while tracking Debug builds as new configurations.
• Added BuildConfig environment variable for MSBuild payload preparation

eng/performance/maui_scenarios_android.proj

• Added -c $(BuildConfig) to pre.py publish command

eng/performance/maui_scenarios_ios.proj

• Changed hardcoded -c Release to -c $(BuildConfig)

eng/pipelines/sdk-perf-jobs.yml

• Added 8 duplicate job definitions with buildConfig: debug for all existing MAUI scenarios:
  • Android: Mono ProfiledAOT, Mono AOT, CoreCLR JIT/R2R/R2RComposite/NativeAOT
  • iOS: Mono FullAOT, CoreCLR NativeAOT

Original prompt

We want to add debug configured runs to the current testing we are doing for the apps in the maui_scenarios_android.proj and the maui_scenarios_ios.proj files. Can you come up with some solutions to getting properly setup debug builds (via passing -c debug into the python pre.py publish command)? The first approach that comes to mind would be to take advantage of the BuildConfig job parameter at the sdk-perf-jobs.yml jobParameters level, passing through buildConfig: debug on a duplicate set of the mobile jobs. Than we could update get_run_configurations in run_performance_job.py to include "BuildConfig" as a configuration for the maui_scenarios_android and maui_scenarios_ios run_kinds. Finally, the _BuildConfig would be passed into the pre.py publish command as the configuration. We would also add this as a part of the RunConfig as string property.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[LoopedBard3]

@copilot please update the two new lines like:

if build_config is not None:
            configurations["BuildConfig"] = build_config

to instead only add BuildConfig to the configurations when it is not the default value. This will ensure we don't break the current trends we have and instead make it so that these are just new configs when running as Debug.

[Copilot]

@copilot please update the two new lines like:

...

Updated to only add BuildConfig when it's not the default value (Release). This ensures existing release builds maintain current trends while debug builds are tracked as new configurations. Changes in commit 75f76c6.

[LoopedBard3]

There are a few issues being seen in the test run (https://dev.azure.com/dnceng/internal/_build/results?buildId=2884653&view=results):

• Device startup failing. The apps are properly made but something (possibly different between the devices) is causing the device startup tests to fail while most of the SOD tests seem to succeed.
• CSC : warning AD0001: Analyzer 'ILLink.RoslynAnalyzer.DynamicallyAccessedMembersAnalyzer' threw an exception of type 'System.MissingMethodException' with message 'Method not found: 'Microsoft.CodeAnalysis.IParameterSymbol Microsoft.CodeAnalysis.ITypeSymbol.get_ExtensionParameter()'.'. [/Users/runner/work/1/s/performance/CorrelationStaging/payload/performance/src/scenarios/netios/app/NetiOSDefault.csproj]. Already tracked [NETSDKE2E][Regression]With 11.0.100-preview.1.26070.110 SDK installed, warning AD0001 appears when publish console project using PublishSingleFile=true in CLI. sdk#52599
• Version extraction is failing for debug due to path issue: Cannot find Mono.Android.dll in ./app/obj/Release/net11.0-ios/ios-arm64/linked. Skipping version extraction. (Working on a fix for this).
• [2026/01/21 22:35:41][INFO] [2026/01/21 22:35:41][INFO] D:\a\1\s\performance\CorrelationStaging\payload\dotnet\packs\Microsoft.Android.Sdk.Windows\36.1.99-ci.main.92\targets\Microsoft.Android.Sdk.AssemblyResolution.targets(198,5): error MSB4096: The item "obj\Debug\net11.0-android\android-arm64\NetAndroidDefault.pdb" in item list "ResolvedSymbols" does not define a value for metadata "DestinationSubPath". In order to use this metadata, either qualify it by specifying %(ResolvedSymbols.DestinationSubPath), or ensure that all items in this list define a value for this metadata. [D:\a\1\s\performance\CorrelationStaging\payload\performance\src\scenarios\netandroid\app\NetAndroidDefault.csproj] (R2R CoreCLR Debug) complete failure. (Possibly related to Cannot publish android project with ReadyToRun runtime#109004)

I am working on the version extraction issue, the first two issues should be followed up in another PR, and I the cause of the last needs to be investigated. @matouskozak do we expect the CoreCLR runs to currently be compatible with building Debug or have you seen this error before?

[LoopedBard3]

Latest PR test run fixed the Version Extraction: https://dev.azure.com/dnceng/internal/_build/results?buildId=2885485&view=logs&j=1d97bf9c-ba2d-53d3-bdd3-7b15b8044ae4&t=5d9c0cfc-3317-59fc-fd95-b8aec0e8a6bb.

[LoopedBard3]

I went ahead and disabled the R2R Debug jobs as they are failing so we can start getting some results for this. The issues that need to be tracked include:

• Device startup failing. The apps are properly made but something (possibly different between the devices) is causing the device startup tests to fail while most of the SOD tests seem to succeed.
• CSC : warning AD0001: Analyzer 'ILLink.RoslynAnalyzer.DynamicallyAccessedMembersAnalyzer' threw an exception of type 'System.MissingMethodException' with message 'Method not found: 'Microsoft.CodeAnalysis.IParameterSymbol Microsoft.CodeAnalysis.ITypeSymbol.get_ExtensionParameter()'.'. [/Users/runner/work/1/s/performance/CorrelationStaging/payload/performance/src/scenarios/netios/app/NetiOSDefault.csproj]. Already tracked [NETSDKE2E][Regression]With 11.0.100-preview.1.26070.110 SDK installed, warning AD0001 appears when publish console project using PublishSingleFile=true in CLI. sdk#52599
• D:\a\1\s\performance\CorrelationStaging\payload\dotnet\packs\Microsoft.Android.Sdk.Windows\36.1.99-ci.main.92\targets\Microsoft.Android.Sdk.AssemblyResolution.targets(198,5): error MSB4096: The item "obj\Debug\net11.0-android\android-arm64\NetAndroidDefault.pdb" in item list "ResolvedSymbols" does not define a value for metadata "DestinationSubPath". In order to use this metadata, either qualify it by specifying %(ResolvedSymbols.DestinationSubPath), or ensure that all items in this list define a value for this metadata. [D:\a\1\s\performance\CorrelationStaging\payload\performance\src\scenarios\netandroid\app\NetAndroidDefault.csproj] (R2R CoreCLR Debug) complete failure. (Possibly related to Cannot publish android project with ReadyToRun runtime#109004)

I did also confirm that the BuildConfig=Debug RunConfiguration item is present.

[LoopedBard3]

This partially completes: #5061