-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Comments
@jeromelaban We will look into the issue and keep you posted with updates. |
We noticed the same issue happening in our e2e pipeline starting yesterday with |
Same problem here. Any news? It's kinda blocking |
+1 |
Hi All, We are still investigating the issue. Will keep you posted with updates soon. |
Observed this issue today and all our build and automation pipelines are failing. @sureshe456 @susmitamane please fix this issue. |
Is there an ETA? We're in serious troubles and we're starting to consider rolling back to physical device for building @sureshe456 @susmitamane |
Hi All, We are still checking on it. will be posted any updates. |
Hi @jeromelaban, |
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 |
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 |
This could make sense, however, even selecting Also, regardless of the selected emulator, even running Furthermore, as noted by others in the thread, the images you mention are not on azure devops, only GHA. |
The Simulators worked fine the day before this issue was posted. What changed? Did something update? |
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. |
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. |
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.
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 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! |
Description
When starting the iOS simulators on macos-15, the following assertion happens:
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
Runner images affected
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:
Repro steps
Run the following pipeline:
The text was updated successfully, but these errors were encountered: