We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(Related: #47)
I'm not sure if this is by design, but the Android workload adds a .sentinel file to ./sdk/, and the iOS one doesn't:
.sentinel
./sdk/
Consequently, only installing the SDK and the iOS workload will result in the "The target platform identifier ios was not recognized" error.
If this is intended, the README should make it clearer that building the iOS sample on macOS will fail unless you also install the Android workload.
The text was updated successfully, but these errors were encountered:
We are hoping the need for a .sentinel file at all can go away.
The dotnet/sdk did this so they could ship workload support behind a feature flag in .NET 5. I think they can get rid of it soon.
Sorry, something went wrong.
In .NET 6 Preview 4, EnableWorkloadResolver.sentinel is no longer needed.
EnableWorkloadResolver.sentinel
No branches or pull requests
(Related: #47)
I'm not sure if this is by design, but the Android workload adds a
.sentinel
file to./sdk/
, and the iOS one doesn't:Consequently, only installing the SDK and the iOS workload will result in the "The target platform identifier ios was not recognized" error.
If this is intended, the README should make it clearer that building the iOS sample on macOS will fail unless you also install the Android workload.
The text was updated successfully, but these errors were encountered: