You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment:
OS: macOS Sierra 10.12.6
Node: 8.7.0
Yarn: Not Found
npm: 5.4.2
Watchman: Not Found
Xcode: Xcode 9.0 Build version 9A235
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.50.0-rc.0 => 0.50.0-rc.0
Target Platform: iOS (11.0)
Steps to Reproduce
tl;dr - It's a brand new react-native app with the latest 0.50.0-rc.0 and react 16 releases.
Install the latest version of react-native-cli: npm i -g react-native-cli
Initialise a new project with the RC version of react-native: react-native init reactapp --version 0.50.0-rc.0
Start the iOS simulator with the unmodified app: cd reactapp && node_modules/.bin/react-native run-ios --simulator="iPhone 8"
Somehow cause a warning to pop up (the attached video uses a minimised Chrome with the remote debugger tab to trigger the "Remote debugger is in a background tab" warning, but a console.warn() will do, too)
Click on the warning
Click Dismiss All (nothing happens)
Click Minimize (nothing happens)
Click Minimize again -> Another warning opens up about using setState() on unmounted component
Expected Behavior
The Dismiss All button would dismiss all warnings
No new warnings are triggered as a result of attempting to dismiss current or all warnings
Actual Behavior
The Dismiss All button does not dismiss the current warning
After clicking Minimize as a result of failed "Dismiss All" attempts, new warning about using setState() on an unmounted component are triggered and opened in full details on the screen
Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
Steps to Reproduce
react-native-cli
:npm i -g react-native-cli
react-native init reactapp --version 0.50.0-rc.0
cd reactapp && node_modules/.bin/react-native run-ios --simulator="iPhone 8"
console.warn()
will do, too)setState()
on unmounted componentExpected Behavior
Actual Behavior
setState()
on an unmounted component are triggered and opened in full details on the screenReproducible Demo
Git repository
git clone https://github.com/robertrossmann/reactapp-bug-report-setstate
npm start
setState()
Screenshot with the error:
Video:
react-native-yellowbox-issue.zip
The text was updated successfully, but these errors were encountered: