Fix iOS nuget XCFramework nested path copy reference #271
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.
Description
One Line Summary
Fixes "OneSignal.xcframework has an incorrect or unknown format and cannot be processed" error on 4.0.0-beta1+ on iOS builds due to wrong copy path for the root
contents
folder whereOneSignal.xcframework
lives under.Details
Our
.nuspec
places theOneSignal.iOS.Binding\Com.OneSignal.targets
file underbuild\Xamarin.iOS10\
in the package so in order for it to accesscontents
at the root it needs to go up two folder levels.PR #255 where this copy command was originally added had this path wrong.
Motivation
Fixes iOS build error reported by beta testers #262 (comment)
Scope
Effects all iOS builds.
Testing
Manual testing
Tested on Visual Studio Community 2019 for Mac and locally modifying
~/.nuget/packages/com.onesignal/4.0.0-beta2/build/Xamarin.iOS10/Com.OneSignal.targets
to confirm it fixes the build and runs on an iOS 14 device.This change is