[infra][iOS][tvOS] Update Apple mobile OS versions used for CI testing to 18.x

[matouskozak]

To keep up with the evolving Apple ecosystem and strict update policy we should update the testing infrastructure to the most current OS used by customers.

Currently, we are running tests on macOS 13.6.3, XCode 14.3, iOS 16.5 (or tvOS 16.3) on osx.13.amd64.iphone.open and osx.13.amd64.appletv.open queues.

We should update these queues to:

• macOS 15.x
• XCode 16.x
• iOS/tvOS 18.x

To ensure smooth transition, we have scouting queues (osx.amd64.iphone.scouting.open, osx.amd64.appletv.scouting.open) which can be updated to the desired configuration and used for testing purposes before the full migration.

After the verification on scouting queues is done, we should reach out to the Helix team to align on the update schedule for the osx.13.amd64.iphone.open and osx.13.amd64.appletv.open queues.

Upgrade to the latest version iOS/tvOS 18.x:

• [Apple mobile] Smoke tests crash in full AOT mode with plt_entry assertion on iOS/tvOS 18.x #117159
• Upgrade osx.amd64.iphone.scouting.open/osx.amd64.appletv.scouting.open queues to iOS/tvOS 18.x
• Create a new Helix queue for MAUI with the same configuration as the runtime queue

Upgrade process automation (repeat annually)

• October: Upgrade the scouting queues to the latest version
• March: Upgrade the default queues to the latest version

---

Note

The same queues (osx.13.amd64.iphone.open and osx.13.amd64.appletv.open) are used for servicing branches. Consequently, any changes to these queues must be validated to be compatible with servicing CI infrastructure.

[dotnet-policy-service]

Tagging subscribers to 'os-ios': @vitek-karas, @kotlarmilos, @ivanpovazan, @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

Tagging subscribers to 'os-tvos': @vitek-karas, @kotlarmilos, @ivanpovazan, @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

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

[missymessa]

DDFUN ticket here: https://portal.microsofticm.com/imp/v5/incidents/details/649965930/summary?tmpl=p3519A

[missymessa]

Feedback from @v-parose about this change:

Will these be moving to a new Helix queue to reflect the OS version change? For example "osx.13.amd64.iphone.open" to "osx.15.amd64.iphone.open" - @kotlarmilos @matouskozak

The Helix deployment script, which is maintained by dotnet installs Xcode as part of Helix onboarding, who should I confirm with that the correct Xcode version is being installed by the script? @epananth who should handle this?

More of an FYI but for the iOS/TVOS versions, only the latest released version can be upgraded to on the devices. If you need a specific version that is not the latest, it will likely not be possible to install.

[kotlarmilos]

Will these be moving to a new Helix queue to reflect the OS version change? For example "osx.13.amd64.iphone.open" to "osx.15.amd64.iphone.open" - @kotlarmilos @matouskozak

Yes, we want to switch to the osx.15 queues once we’ve confirmed that the tests pass on the new version. Are osx.15.amd64.iphone and osx.15.amd64.appletv queues ready?