Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[azure devops] AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Assert: platformExpert, value: 0 #10925

Open
2 of 15 tasks
jeromelaban opened this issue Nov 7, 2024 · 17 comments

Comments

@jeromelaban
Copy link

jeromelaban commented Nov 7, 2024

Description

When starting the iOS simulators on macos-15, the following assertion happens:

AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Assert: platformExpert,  value: 0
AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Failed to get AppleVirtualPlatformARMPE service.

The message shows up as stdout, "polluting" machine readable outputs like simctl.

This is azure devops specific, this does not happen on github actions with macos-15.

Related to #10918

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

20241106.316

Is it regression?

Not for this image, but compared to other images, yes.

Expected behavior

No assertions in the log

Actual behavior

Many messages like this one:

AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Assert: platformExpert,  value: 0
AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Failed to get AppleVirtualPlatformARMPE service.

Repro steps

Run the following pipeline:

pool:
  vmImage: 'windows-2022'

trigger:
  - main

stages:
- stage: Setup
  jobs:
  - job: Pipeline_Validations

    pool:
      vmImage: 'macos-15'

    steps:
    - checkout: self
      clean: 'true'
      fetchDepth: 0

    - bash: |
        /bin/bash -c "sudo xcode-select -s /Applications/Xcode_16.app/Contents/Developer"
  
        echo "Listing iOS simulators"
        xcrun simctl list devices --json
  
        export SIMULATOR_VERSION="com.apple.CoreSimulator.SimRuntime.iOS-18-1"
        export SIMULATOR_NAME="iPad Pro 13-inch (M4)"
  
        export UITEST_IOSDEVICE_ID=`xcrun simctl list -j | jq -r --arg sim "$SIMULATOR_VERSION" --arg name "$SIMULATOR_NAME" '.devices[$sim] | .[] | select(.name==$name) | .udid'`
        xcrun simctl boot $UITEST_IOSDEVICE_ID
  
        sleep 300
      name: Run
@susmitamane
Copy link
Contributor

@jeromelaban We will look into the issue and keep you posted with updates.

@topi-identio
Copy link

topi-identio commented Nov 8, 2024

We noticed the same issue happening in our e2e pipeline starting yesterday with macOS-15 as well. It happens with both iOS 18.0 and 18.1 Simulators.

@albertoAround
Copy link

Same problem here. Any news? It's kinda blocking

@examplecodecn
Copy link

+1

@sureshe456
Copy link
Contributor

Hi All, We are still investigating the issue. Will keep you posted with updates soon.

@sanket492
Copy link

Observed this issue today and all our build and automation pipelines are failing. @sureshe456 @susmitamane please fix this issue.

@albertoAround
Copy link

Is there an ETA? We're in serious troubles and we're starting to consider rolling back to physical device for building @sureshe456 @susmitamane

@sureshe456
Copy link
Contributor

Hi All, We are still checking on it. will be posted any updates.

@sureshe456
Copy link
Contributor

Hi @jeromelaban,
Based on the analysis, the macos-15-large (macos-15) is based on an AMD64 processor, while the macos-15-xlarge (macos-15-arm64) is based on an ARM64 processor. The AppleVirtualPlatformARMPE service is specifically designed for Apple Silicon (ARM-based) processors, such as the M1, M1 Pro, M1 Max, M2, and later chips. It is not compatible with AMD64 (x86_64) processors.
Therefore, when you start iOS simulators on macos-15 (AMD64 processor), then AppleVirtualPlatformARMPE service will be inaccessible. However, this service will be accessible on the macos-15-xlarge (macos-15-arm64) image.

@albertoAround
Copy link

So what kind of image do we have to type? I tried macos-15-arm64 and macos-15-xlarge but I received for both the same error

"No config name or imagelabel provided in request" @sureshe456

@sureshe456
Copy link
Contributor

For macOS 15 Arm64: Please try with this macos-15.
FYI...
Screenshot 2024-11-15 at 8 33 25 PM

@albertoAround
Copy link

We're working on Azure hosted images. So here are the ones that we can pick https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml

There is no macos-15-large or xlarge. @sureshe456

@jeromelaban
Copy link
Author

Therefore, when you start iOS simulators on macos-15 (AMD64 processor), then AppleVirtualPlatformARMPE service will be inaccessible. However, this service will be accessible on the macos-15-xlarge (macos-15-arm64) image.

This could make sense, however, even selecting iPad (10th generation) does not work.

Also, regardless of the selected emulator, even running xcrun simctl list devices --json will emit the messages.

Furthermore, as noted by others in the thread, the images you mention are not on azure devops, only GHA.

@topi-identio
Copy link

The Simulators worked fine the day before this issue was posted. What changed? Did something update?

@albertoAround
Copy link

I mean, it's two weeks that we can't build... From such a large company it's almost unbelievable and we are paying for this service.

@sureshe456
Copy link
Contributor

Hi All, We apologize for the inconvenience and understand the frustration this has caused. There was an issue with patches update on macOS 15 image generation.So, our team is actively working on resolving the issue, and we appreciate your patience during this time. Thank you for bringing this to our attention. We will keep you updated with any new information.Thanks.

@wimdows-nl
Copy link

wimdows-nl commented Nov 22, 2024

Exactly same problem here, but getting this on Azure DevOps, after XCode 16 was removed from MacOS 15 build agents, and we had to specify MacOS 15 instead to use XCode 16.

AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Assert: platformExpert,  value: 0
AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Failed to get AppleVirtualPlatformARMPE service.
** ARCHIVE FAILED **

It only seems to happen on Mac OS 15 images that are on version 15.0.1. Specifically: https://github.com/actions/runner-images/releases/tag/macos-15%2F20241022.244

However, the same image tag 'macOS-15' sometimes results in an agent which has Mac OS 15.1 installed, see
here: https://github.com/actions/runner-images/releases/tag/macos-15%2F20241106.316

So the solution may just be to ensure all 'macOS-15' agents on Azure DevOps (and possibly on for Github actions agents too) are updated to MacOS 15.1 (image version 20241106.316) minimum.

Hope that helps!

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

No branches or pull requests

8 participants