Can't call setState (or forceUpdate) on an unmounted component
See original GitHub issueHi
I created a FluidNavigator and included it in a DrawerNavigator like so.
const ReceiptsNavigator = FluidNavigator({
AllReceiptsScene: { screen: AllReceiptsScene },
ReceiptScene: { screen: ReceiptScene },
});
const screens = {
Home: {
screen: HomeNavigator,
},
Receipts: {
screen: ReceiptsNavigator
},
/*etc*/
}
const RootNavigator = createDrawerNavigator(screens, {
/*some options*/
})
Everything works well within the FluidNavigator but sometimes when I navigate out of it I get this error
C:\git\HausMart\minibar-client-mobile\node_modules\react-native\Libraries\Core\ExceptionsManager.js:71 Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
in TransitionItemsView (at FluidTransitioner.js:204)
in RCTView (at View.js:60)
in View (at Transitioner.js:169)
in Transitioner (at FluidTransitioner.js:69)
in FluidTransitioner (at createFluidNavigator.js:35)
in FluidNavigationView (at createNavigator.js:57)
in Navigator (at createNavigationContainer.js:383)
in NavigationContainer (at SceneView.js:10)
Any ideas? 😃
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Can't call setState (or forceUpdate) on an unmounted ...
Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application....
Read more >Prevent React setState on unmounted Component
Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application....
Read more >Prevent React setState on unmounted component - Martin Belev
Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application...
Read more >Can't call setState (or forceUpdate) on an unmounted ... - GitHub
Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application....
Read more >Fixing React's “Called SetState() on an ... - How-To Geek
Seeing called setState() on an unmounted component in your browser console means the callback for an async operation is still running after a ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I see that the PR is closed, has this been added to a release? Because I still get this error.
@Dagurmart A fix should be available in pr #107.