Closed MartinZikmund closed 2 weeks ago
17.0.8523
Is TargetFramework=net8.0-ios17.0
in your app project?
@rolfbjarne Yes, I was using net8.0-ios17.0
. In the repro steps I mention that net8.0-ios
should be used in the target framework override file, but in another .props
file we then replace it with net8.0-ios17.0
@rolfbjarne Yes, I was using
net8.0-ios17.0
. In the repro steps I mention thatnet8.0-ios
should be used in the target framework override file, but in another.props
file we then replace it withnet8.0-ios17.0
Is there any particular reason you're using net8.0-ios17.0
as opposed to net8.0-ios
? By using the 17.0 version, you pick up an older version of the iOS workload, which has this bug. Using net8.0-ios
will use the latest version of the iOS, where the bug is fixed.
Hi @MartinZikmund. We have added the "need-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.
I can confirm I am now able to build and deploy the app with Visual Studio 2022 17.12 Preview. For VS 17.11.1 I have hit another, likely unrelated issue - https://developercommunity.visualstudio.com/t/Unable-to-build-iOS-app-on-remote-Mac:-/10732362 .
Thanks a lot for the help!
@rolfbjarne Yes, we are using the oldest supported version so that users using older .NET SDK versions don't break. That's basically why we wanted https://github.com/dotnet/sdk/issues/30103
@rolfbjarne Yes, we are using the oldest supported version so that users using older .NET SDK versions don't break. That's basically why we wanted dotnet/sdk#30103
There's a difference between a library project and an executable project - using an earlier TargetFramework version makes sense for a library project, because you're keeping compatibility with consumers of that library project. Nobody is consuming an executable project though, so for executable projects we recommend using the latest TargetFramework (or the default).
Ah okay, this bug is only relevant for executables? We can fix it on our side. We were aligning TargetFramework for all projects in the solution, but we can only do it for libraries.
Ah okay, this bug is only relevant for executables? We can fix it on our side. We were aligning TargetFramework for all projects in the solution, but we can only do it for libraries.
It's more that using the earliest TargetFramework is only relevant for libraries (and this bug won't affect library builds).
Apple platform
iOS
Framework version
net8.0-*
Affected platform version
VS 2022 17.11.1
Description
When trying to build and run iOS Uno Platform test application on iOS Simulator, we are suddenly getting the following error in VS 2022 17.11.1:
When trying the same in VS 2022 17.12.0 Preview, I got exactly the same error as in https://github.com/xamarin/xamarin-macios/issues/21005 instead
Steps to Reproduce
Did you find any workaround?
No
Build logs
The app project is
SamplesApp.netcoremobile_Debug_AnyCPU
all.zip