-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
When runtime adds Cocoapods, it should include 'i386' as architecture options #536
Comments
Sample of errors resulting from not including i386 as build architecture option:
|
Hi @NathanWalker |
@ivanbuhov Thanks for your help. I've tried this but doesn't seem to work or I'm not doing it correctly.
Result: Doesn't appear to change anything.
Result: It does add to the .xcconfig correctly but it results in the same error above. (
Result: Same error still. Any other suggestions? Or help me understand what is going on. Pretty frustrating. |
My idea was to take advantage of the CLI support for merging |
Thanks @ivanbuhov you've been very helpful. I'm going to try the brave new ground with XCode 7.3 just released yesterday actually. If that doesn't work, I'll downgrade. |
Ok so I just tried 7.3 and it works and fixes this issue! Hooray! 👍 I'll close this in favor of the new one, hopefully a new ios-runtime can be released to fix that for 7.3 and all will be good. |
For instance, this Cocoapod:
https://github.com/NathanWalker/MaterialCard
Can be setup as a plugin with a Podfile:
And when run via
tns emulate ios
, it fails because the Simulator requiresi386
architecture and pod setups by default only specify the various standard$(ARCHS_STANDARD)
flavors likearm64 armv7 armv7s
.The runtime should automatically ensure that
i386
architecture is added for CocoaPods when installing and running them in the Simulator.Worth noting that using
tns run ios
with a iPhone connected runs just fine.So it's definitely isolated to running in the Simulator.
The pod is used here:
https://github.com/bradmartin/nativescript-cardview
Holding off on releasing a new version until I can get some feedback here on what's going on with the aforementioned.
Please help provide insight here if anyone knows?
The text was updated successfully, but these errors were encountered: