search

react-native-community / upgrade-support

A central community-backed place to request and give help when upgrading your app.
MIT License
261 stars 2 forks source link

TypeError: _this7._config.server.rewriteRequestUrl is not a function React native 0.64.0 #169

Open San10694 opened 3 years ago

San10694 commented 3 years ago

Environment

System: OS: macOS 11.2.3 CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Memory: 1.59 GB / 16.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 14.16.0 - /usr/local/bin/node Yarn: 1.12.3 - /usr/local/bin/yarn npm: 6.14.11 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2 Android SDK: API Levels: 23, 27, 28, 29 Build Tools: 27.0.3, 28.0.3, 29.0.2, 29.0.3 System Images: android-27 | Google Play Intel x86 Atom Android NDK: Not Found IDEs: Android Studio: 4.1 AI-201.8743.12.41.7042882 Xcode: 12.4/12D4e - /usr/bin/xcodebuild Languages: Java: 1.8.0_271 - /Library/Java/JavaVirtualMachines/jdk1.8.0_271.jdk/Contents/Home/bin/javac npmPackages: @react-native-community/cli: Not Found react: 17.0.1 => 17.0.1 react-native: 0.64.0 => 0.64.0 react-native-macos: Not Found npmGlobalPackages: react-native: Not Found.

Things I’ve done to figure out my issue

Upgrading version

0.64.0

Description

I have upgraded one of my react-native iOS app from 0.62.0 to 0.64.0, I updated all the dependencies described in the upgrade helper then ran yarn install followed by Pod Install. I am able to make debug build on iOS but getting a red screen as soon as the app launches.

simulator_screenshot_1644D976-04B3-4F7E-99BF-5777C71BA05C

-->

Reproducible demo

dishpanda commented 3 years ago

Were you able to find a solution to this issue?

San10694 commented 3 years ago

@dishpanda no still struggling can anyone please help here

amleonardccsd commented 3 years ago

What does your package.json look like? I I had a "resolution" field with metro-config 0.57.0 in it, and that was overriding the version of metro-config that metro needs.

AdityaPahilwani commented 2 years ago

@amleonardccsd how did you solved it? I tried to remove mero-confif from resolution field still faces the same issue

AdityaPahilwani commented 2 years ago

I would suggest to bump up your metro version.

I faces a similar issue and the issue was with metro version conflicts.

Our metro version was 0.56 and when migrating from 0.63 to 0.64 and @react-native-community/cli metro version gets bumped to 0.64.0.

Because of this metro resolution was failing and threw this error