Problem with XCode 14 and m1 mac. #232
Comments
|
I'm having this same problem with XCode 14 on a M1 Macbook Pro. EDIT: Realized I should mention that this problem does indeed go away if I downgrade to xCode 13. Would like to stay on xCode 14, however, as I want to test applications on an iPhone 14. |
|
I am having this issue too. The fix that @clintmod provides it works. |
|
Confirming only works with Xcode 13 |
|
Facing the same issue, too. Tried ruby versions 2.7.4, 2.7.6 and 3.1.2. Tried Xcode 14.0.1 and 13.4.1. Nothing works. Is there a specific Xcode 13 version I need to use? |
|
@fabianmuecke I tried ruby 2.7.4 with Xcode 13.4.1. Don't forget to change Xcode select to 13 version. |
|
Thanks @josorio-uber. In the end, the problem seemed to be related to my rbenv somehow. I uninstalled rbenv and installed Ruby 3.1.2p20 via brew. That solved the problem and I can now even use Xcode 14.0.1. No idea why, though. 🤷♂️ |
|
It's worth mentioning that once it's compiled with Xcode 13 the ruby_inline lib caches the results in |
|
#217 (comment) |
|
[!] Your Podfile requires that the plugin I have this error in M1 MAX & Monterey 12.6.1 & XCode 14.1 I couldn't solve this problem with all possible solutions |
|
In my case I encountered this issue, trying to run |
|
@mattneub |
|
After a quick look at different keychain gems, I'd recommend someone take a look at switching this gem to use https://rubygems.org/gems/ruby-keychain |
|
I've managed to install and use cocoapods-keys on Apple M1 Max chip. It worked for me with System ruby installation combined with Xcode 13.4.1. I also tried out different ruby versions using rbenv, but without any luck. The best is that I can still use arm64 terminal, and no need to start reinstalling everything under Rosetta. 🎉 OS details: Ruby version |
|
@kdlogen The problem is that if you're using macOS 13 (Ventura) there is no such thing as Xcode 13. |
|
Totally same issue, it annoyed me for this whole week. Fortunately the error goes away this afternoon - although I'm not sure it was what that make it work. |
|
We've had this problem in another gem that uses
The key to getting it working under Xcode 14 is linking ruby library. We can force do that by specifying LDFLAGS in install command:
Why this works under Xcode 13 I am not sure, maybe there was some change in clang's behaviour, but I couldn't find it. |
|
I rewrote the plugin with another ruby-keychain gem. All tests are working too. I just didn't have time to test/implement it in my projects over the weekend (to validate legacy support). Just to let you know! :) #235 |
|
We solved the problem in our app by switching to another keychain gem, but on behalf of our entire company (unauthorized, this is just me talking) I'd like to thank @orta for making this utility available. It has done good service and our entire build process depended on it for years. |
I just had to set up a couple of new m1 build machines and I couldn't get this gem to run the ruby-inline c++ code when running
pod installwith XCode 14.I was able to work around this by downgrading to Xcode 13.
Here was the error:
I actually tried to force an
x86_64build to see if that would fix it witharch -x86_64 pod installbut it still complained about not being able to find the exact same symbols. I wonder if the ruby framework in Xcode 14 changed.Wanted to also mention that I'm installing ruby with
rbenvand that I did downgrade ruby from 3 to 2 although I'm not sure that the ruby downgrade was required.The text was updated successfully, but these errors were encountered: