-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Issue with thinning dSYM files #7196
New issue
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
Comments
You should also contact the pod author to ship a fat |
Thanks for quick response - I suspect they've excluded the simulator dSYM slices due to the overall size of their vendors contents which is over 1GB. |
@mwoollard can you try this patch from this PR #7197? |
Merged. |
Confirmed PR #7197 resolves issue. Now builds with suitable warning:
Thanks for prompt resolution! |
Report
What did you do?
integrate a project with
ArcGIS-Runtime-SDK-iOS
podpod install
Followed by building of resulting workspace in Xcode for simulator
What did you expect to happen?
Project to build and run on simulator
What happened instead?
When building for simulator environment project failed whilst running
[CP] Embed Pod Frameworks
step. The above pod vendors a binary static framework that includes dSYM files but there are only FAT slices for device architectures not simulator. When building for simulator the script fails when stripping the last device architecture lipo fails.fatal error: lipo: -remove's specified would result in an empty fat file
When building for device rather than simulator the build succeeds since the device slices are not removed. Note that commenting out:
strip_invalid_archs "$binary"
For the dSYM files allowed the app to build and run in the simulator.
Can this case be detected and the dSYM copy skipped rather than failing with the above error?
CocoaPods Environment
Stack
Installation Source
Plugins
Podfile
Project that demonstrates the issue
A project to reproduce issue available here:
https://github.com/mwoollard/cpbug.git
The text was updated successfully, but these errors were encountered: