Added backwards compatibility for locating provisioning stuff in legacy Xamarin folders #136
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cy Xamarin folders Dev17 still generates provisioning information in the legacy Xamarin paths, so we need a way for this code to consider both new and legacy paths. This fixes an issue where Dev17 fails to build with newer iOS SDK versions that relies only on new MAUI paths. The reason of the failure is because Dev17 uses legacy paths and the iOS SDK looks in new paths. Fixes P0 bug #2505126
emaf
approved these changes
Jun 23, 2025
mauroa
added a commit
to dotnet/macios
that referenced
this pull request
Jun 23, 2025
Brings an important P0 fix for VS 17.14: dotnet/macios-devtools#136 Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2505126
dalexsoto
pushed a commit
to dotnet/macios
that referenced
this pull request
Jun 23, 2025
Brings an important P0 fix for VS 17.14: dotnet/macios-devtools#136 Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2505126
dalexsoto
added a commit
to dotnet/macios
that referenced
this pull request
Jun 24, 2025
Backport of #23136 Brings an important P0 fix for VS 17.14: dotnet/macios-devtools#136 Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2505126 Co-authored-by: maagno <[email protected]>
dalexsoto
pushed a commit
to dotnet/macios
that referenced
this pull request
Jun 24, 2025
Brings an important P0 fix for VS 17.14: dotnet/macios-devtools#136 Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2505126
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dev17 still generates provisioning information in the legacy Xamarin paths, so we need a way for this code to consider both new and legacy paths. This fixes an issue where Dev17 fails to build with newer iOS SDK versions that relies only on new MAUI paths. The reason of the failure is because Dev17 uses legacy paths and the iOS SDK looks in new paths.
Fixes P0 bug #2505126