rolfbjarne
commented
2 weeks ago 3. Add
ForceSimulatorX64ArchitectureInIDEto the csproj file, in an attempt to always build for simulator using the x64 architecture (as was the case when targettingnet7.0-ios) 4. Try to build (ex. from command line, usingdotnet build)
As the property name ForceSimulatorX64ArchitectureInIDE says, it only affects in IDE builds (not command line builds). So the behavior you're explaining is expected.
When building from the command line, you can pass the runtime identifier like this:
$ dotnet build /p:RuntimeIdentifier=iossimulator-x64in order to build for the x64 simulator.
That said, it sounds like you're seeing the same behavior in an IDE - can you confirm this? And which IDE you're using?
sasha-borodin
Steps to Reproduce
ForceSimulatorX64ArchitectureInIDEto the csproj file, in an attempt to always build for simulator using the x64 architecture (as was the case when targettingnet7.0-ios)dotnet build)Expected Behavior
Build process builds for simulator using
x64architecture.Actual Behavior
Build process attempts to build for simulator using
arm64architecture, and errors out with one or more of the following:Environment
Version information
Build Logs
Example Project (If Possible)
n/a
Additional Comments
The suggestion from official documentation here is to specify Runtime Identifiers. However, I can't figure out a way to do this in such a way that debugging works on both simulator and physical device. For example, if I specify something like...
...this will work great when debugging on a physical device, but not the simulator (and vice versa).