-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
IOS build failed with "You may also need to include 'iossimulator-x64' in your project's RuntimeIdentifiers" #23352
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Closed similar issues:
|
There are many people running into this problem. The only workaround as far as I know is to delete the After some time it is broken again, does anyone know a fix by setting the correct runtime when building for a simulator? |
@rolfbjarne thoughts? @RagibNoor |
This is a known issue with VSMac. Here's one example: https://developercommunity.visualstudio.com/t/Assets-file-issue-on-build/10312467 Since VSMac is scheduled for imminent retirement, it won't be fixed, so I would recommend moving to VSCode instead (which doesn't seem to have this problem). |
@PureWeen no addding |
Description
i am unable to run my project on simulator getting following error
In my project i am targeting ios only in runtime , here is my project configuration
I have tried to clean my bin/obj folder restart ide multiple time still no luck .
here is MY VS details
Steps to Reproduce
No response
Link to public reproduction project repository
No response
Version with bug
8.0.40 SR5
Is this a regression from previous behavior?
Yes, this used to work in .NET MAUI
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: