Skip to content

Post 0.43 upgrade: PerfMonitor has no setter or ivar for its bridge #13384

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
fhadsheikh opened this issue Apr 7, 2017 · 12 comments
Closed

Post 0.43 upgrade: PerfMonitor has no setter or ivar for its bridge #13384

fhadsheikh opened this issue Apr 7, 2017 · 12 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@fhadsheikh
Copy link

fhadsheikh commented Apr 7, 2017

Description

After upgrading to React Native version 0.43, getting the red screen with error: "PerfMonitor has no setter or ivar for its bridge, which is not permitted. You must either @synthesize the bridge property, or provide your own setter method".

screen shot 2017-04-07 at 10 04 58 am

Reproduction Steps

Upgraded from version 0.42.3 using react-native-git-upgrade. There were no conflicts. Then ran "react-native link".

Additional Information

  • React Native version: 43
  • Platform: iOS
  • Development Operating System: MacOS
@javache
Copy link
Member

javache commented Apr 7, 2017

It looks like this line is swallowing the original exception: https://github.com/facebook/react-native/blob/master/React/Base/RCTModuleData.mm#L149-L153

Can you comment that try-catch to find the real underlying exception?

@juanviola
Copy link

Hi guys, I'm having the same issue, have you found a way to fix it?

@hyb175
Copy link

hyb175 commented Apr 11, 2017

Resetting the simulator (probably unnecessary) + deleting the ios/build folder worked for me.
And the usual:

watchman watch-del-all
rm -rf node_modules
yarn
npm start -- --reset-cache

@juanviola
Copy link

Awesome, you right. That worked for me!

Thanks

@alfredctchoi
Copy link

The following steps worked for me.

  • clean xcode project
  • stop node package manager
  • rm -rf node_modules
  • yarn
  • restart project in simulator

@bezenson
Copy link

Running via Xcode helped me.

@neopit
Copy link

neopit commented Apr 20, 2017

After trying everything (rm node_module etc, clean, change the version of react-native (higher, lower, ....) dozen times. I can say the only thing WORKING for me is DELETING the IOS/BUILD folder.

Hope that help!.

@MoOx
Copy link
Contributor

MoOx commented Jun 1, 2017

Another solution is via Xcode menu bar : Product > Clean. Worked for me.

@Mindaugas-Jacionis
Copy link

It is odd, because I get this error with RN 0.44.0 and only when running react-native run-ios command from terminal, if I am building using xcode - all is good.

@hyb175
Copy link

hyb175 commented Jun 5, 2017

@Mindaugas-Jacionis That's because xcode and react-native store the built binaries in different folders. react-native stores in your-project-folder/ios/build/, but xcode stores in ~/Library/Developer/Xcode/DerivedData. You need to remove your-project-folder/ios/build/ for react-native to work

@Mindaugas-Jacionis
Copy link

@hyb175 you're awesome! Thanks! :)

@djalmaaraujo
Copy link

@hyb175 Your suggestion worked for me. Thanks.

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests