ios build fails on v1.23.7 - RN >=0.78.0 - new architecture disabled

[angelica-snowit]

Summary

Same issue described here: #5400 (comment)

I just updated from version 1.20.1 to 1.23.7 (a minor release, so it should just work as before), and I am suddenly getting: [!] No podspec found for react-native-google-maps in ../node_modules/react-native-maps running pod install.

Podfile contains (as before the upgrade):

rn_maps_path = '../node_modules/react-native-maps'
pod 'react-native-google-maps', :path => rn_maps_path

RN version: 0.78.0
New architecture obviously disabled (mainly because of this library).

Reproducible sample code

<MapView />

Steps to reproduce

Use se the provided /example project:
RCT_NEW_ARCH_ENABLED=0 pod install in /ios
XCode build

Expected result

iOS build succed

Actual result

iOS build fails with error: [!] No podspec found for react-native-google-maps in ../node_modules/react-native-maps running pod install.

React Native Maps Version

1.23.7

What platforms are you seeing the problem on?

iOS (Google Maps)

React Native Version

0.78.0

What version of Expo are you using?

Not using Expo

Device(s)

iOS simulator

Additional information

No response

[lorenc-tomasz]

Hi,
@salah-ghanim mentioned here: #5467 (comment) that new arch is not supported.

[angelica-snowit]

Ok, so based on the discussion linked, 1.21 supports old arch, 1.22 instead don't support old arch. The problem is not that the new arch is not supported: the problem is that the OLD arch is no more supported.
I would have considered this a breaking change, not a minor.

[salah-ghanim]

@angelica-snowit yes it's a breaking change, will update the docs

[angelica-snowit]

@angelica-snowit yes it's a breaking change, will update the docs

Yes, great to have the docs updated, but semver is fundamental. A major release would not install automatically causing build issues.

[scarlac]

Agree with @angelica-snowit - to make it clear that this was breaking, a new release should have been made. I see several other issues popping up in relation to Expo 54 that are likely caused by this issue due to a lack of documentation around this.

You may want to look into that.