CocoaPods | The Cocoa Dependency Manager | iOS library

There are a number of things to look into.
If you are running Expo in the SDK then no need for cocoa pods just the most up-to-date version of the CLI tool.

Run expo --version to determine what version you are currently working with. Update if needed.

Adding a profile might be useful too. Along with checking your config. Configuring EAS Build with eas.json

eas build --platform ios --profile distribution

Also, be sure that all the apple certificates are active and connected to your Expo account for that project.

This is an issue that occurs in version 13.3 of Xcode. In Xcode 13.3, if you have a code that uses UI_USER_INTERFACE_IDIOM(), you will get an "Out of Memory" error when you run Archive. Changing "UI_USER_INTERFACE_IDIOM()" to "UIDevice.current.userInterfaceIdiom" resolves the error.

Currently, we have the following solutions.

• Modify the code,
• Downgrade to Xcode 13.2.1
• Wait for Apple to modify Xcode

References

• https://developer.apple.com/forums/thread/702200
• https://bugs.swift.org/browse/SR-16003
• https://github.com/longitachi/ZLPhotoBrowser/issues/699

You could create that into the library source or you could avoid it and use the same UIColor option just above it.

I removed: ( [RCTConvert UIColor:options.cancelButtonTintColor() ? @( options.cancelButtonTintColor()) : nil];* ) and replace it with: ( *[RCTConvert UIColor:options.tintColor() ? @(options.tintColor()) : nil]; )

my line now looks like:

The error message says there's a permission issue:

Permission bits for '/Users/myUser/.netrc' should be 0600, but are 644

So in order to fix the permission, you should do this:

I have been facing this same issue for some time now. the same setup is working nicely in a mac with intel chip. But i have even done a resetup of my system, m1 mac still throws the same error.

A response on IssueTracker says

This problem is present with Android Studio Bumblebee on Mac. Launching flutter from the IDE causes this issue where it can't find the Cocoapods path.

Forced to run flutter from terminal for it to work.

Here's how run your project from the CLI on the iOS simulator. cd into your project directory and run:

If You don't use M1 based computer to build, You can comment "__apply_Xcode_12_5_M1_post_install_workaround(installer)" line in Your Podfile.

I fixed it doing this:

I uninstalled completely cocoapods (my version was 1.11.0)

gem list --local | grep cocoapods

cocoapods-core (1.11.0) cocoapods-deintegrate (1.0.5) cocoapods-downloader (1.5.0) cocoapods-plugins (1.0.0) cocoapods-search (1.0.1) cocoapods-trunk (1.6.0) cocoapods-try (1.2.0)

sudo gem uninstall cocoapods

sudo gem uninstall cocoapods-core

sudo gem uninstall cocoapods-deintegrate

sudo gem uninstall cocoapods-downloader

sudo gem uninstall cocoapods-plugins

sudo gem uninstall cocoapods-search

sudo gem uninstall cocoapods-trunk

sudo gem uninstall cocoapods-try

Then i installed cocoapods version 1.10.1 (you can try with more versions under 1.11.0 if you need)

sudo gem install cocoapods -v 1.10.1

I recently encountered a similar issue with boost after updating react native. After the panic wore off, and some good coffee, I was able to resolve by doing the following:

1. Open the /ios/.xcworkspace file in Xcode.
2. Raise the iOS Deployment Target (in my case I only bumped to 10).
3. Product > Clean Build Folder, then Product > Run.
4. Locate the boost error in the issue navigator and identify which pod the error is listed under (in my case it was RNReanimated).
5. Update the node package related to the pod (in my case, npm update react-native-reanimated
6. Finally, run pod install

After performing those steps, I was able to get my project up and running again.