can't build on "react-native": "0.71.3",

[sharifashraful]

Describe the bug
I can't build on "react-native": "0.71.3", error came like this

yarn run v1.22.19
$ cd ios && NO_FLIPPER=1 RCT_NEW_ARCH_ENABLED=0 bundle exec pod install && cd ..
warn Multiple Podfiles were found: ios/Podfile,vendor/bundle/ruby/2.7.0/gems/cocoapods-core-1.11.3/lib/cocoapods-core/Podfile. Choosing ios/Podfile automatically. If you would like to select a different one, you can configure it via "project.ios.sourceDir". You can learn more about it here: https://github.com/react-native-community/cli/blob/master/docs/configuration.md
error Failed to build the app: No package name found. We couldn't parse the namespace from neither your build.gradle[.kts] file at /Users/sharif/envy/envypayments/node_modules/@stripe/stripe-terminal-react-native/android/build.gradle nor your package in the AndroidManifest at /Users/sharif/envy/envypayments/node_modules/@stripe/stripe-terminal-react-native/android/src/main/AndroidManifest.xml.

[!] Invalid `Podfile` file: unexpected token at 'info Run CLI with --verbose flag for more details.
'.

 #  from /Users/sharif/envy/envypayments/ios/Podfile:36
 #  -------------------------------------------
 #  target 'envypayments' do
 >    config = use_native_modules!
 #  
 #  -------------------------------------------

Screenshots
If applicable, add screenshots to help explain your problem.

Stripe Terminal React Native SDK version

• ^0.0.1-beta.17

"react-native": "0.71.3",

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[nazli-stripe]

hey @sharifashraful the main build command and error seems to be for iOS but the terminal error is for Android. What exactly are you running and what's the project structure?

[sharifashraful]

error fixed after upgrading react native version

[DenisDov]

error fixed after upgrading react native version

which react-native version resolved this error for you?