Error "no implicit conversion of String into Array" in Pod Install after migrating to RN > 0.74 (0.74.0 until 0.75.3) about react-native HOT 6 OPEN

from react-native.

from react-native.

@MasGaNo thanks for the issue. The build setting can definitely be either String or Array. I'm not sure if that's due to different versions of Xcode, version of cocoapods, or the method used to actually read the project.

Anyway, I'd like to ask you a couple of things:

1. Could you try run bundle install and then install pods with bundle exec pod install? We use Ruby Bundler to ensure that all the cocoapods dependencies are aligned properly and that might fix your issue
2. Could you create a PR with the fix for this? If we handle them more solidly (using array methods when we receive an array, and strings methods when we receive a string) that would be better for everyone!

Thank you so much.

from react-native.

@cipolleschi Thank you for the quick feedback.
Regarding the first point, I have some issue to run the bundle install command:

make: *** No rule to make target `/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin22/ruby/config.h', needed by `nkf.o'.  Stop.

I'm suspecting the fact I'm using the default Ruby 2.6 from MacOS/XCode and it may lead to some issues. I'm currently trying to replace it by a proper ruby and will let you know.

Regarding the fix itself, I just created the PR with the code snippet I put above and updated the test to support both Array and String value.

Thank you!

from react-native.

1. Could you try run bundle install and then install pods with bundle exec pod install? We use Ruby Bundler to ensure that all the cocoapods dependencies are aligned properly and that might fix your issue

Sorry for the late answer, but I finally managed to execute these commands, the first bundle install went smoothly, but the second one bundle exec pod install led to the same issue describe in my first post.

Hopefully, everything will be solved once the fix will be released 😄

from react-native.