Invalid paths created in IOSPostBuildProcessor on v5.2.0 #181
Description
The iOS Build PostProcessor creates an full path reference to SDK specific files, such that if the folder is moved, the Archive action will fail. This can be problematic for teams who use a CI/CD flow where Xcode projects are moved rather than being built in-place.
This occurred around v5.0, around the same time we reported #144. We had fixed it locally, but just had to apply the same fix to v5.2 when attempting to release a new build with the updated SDK.
Our change to resolve the issue is as follows:
STR
- Create an example iOS test export from a CleverTap project.
- Move the Xcode folder to a new location
- Open the Xcode project and attempt to preform an Archive action.
Result
Project fails to archive with the following error:
17:30:09 error: lstat(/Users/michael/.jenkins/workspace/[REDACTED]Xcode/CleverTapSDK): No such file or directory (2) (in target 'Unity-iPhone' from project 'Unity-iPhone')
Expected
Project folder is able to be relocated and still archives successfully.