React Lifecycle
This guide discusses how to use the Ionic Lifecycle events in an Ionic React application.
#
Ionic Lifecycle MethodsIonic provides a few lifecycle methods that you can use in your apps:
Event Name | Description |
---|---|
ionViewWillEnter | Fired when the component routing to is about to animate into view. |
ionViewDidEnter | Fired when the component routing to has finished animating. |
ionViewWillLeave | Fired when the component routing from is about to animate. |
ionViewDidLeave | Fired when the component routing to has finished animating. |
The way you access these methods varies based on if you are using class-based components or functional components. We cover both methods below.
#
Lifecycle Methods in Class-Based Componentsto use the Ionic Lifecycle methods in a class-based component, you must wrap your component with the withIonLifeCycle
higher order component (HOC) like so:
withIonLifeCycle
is imported from@ionic/react
You can then create the appropriate lifecycle method on your class component, and the HOC calls that method when the event happens. Below is the entire component with each of the lifecycle methods implemented:
#
Lifecycle Methods in Functional ComponentsIonic React exports hooks for each of the lifecycle methods that you can use in your functional components. Each of the hooks takes the method you want called when the event fires.
Note: Functional components don't need to be wrapped with the
withIonLifeCycle
HOC as class components do.
#
React LifeCycle MethodsAll the lifecycle methods in React (componentDidMount
, componentWillUnmount
, etc..) are available for you to use as well. However, since Ionic React manages the lifetime of a page, certain events might not fire when you expect them to. For instance, componentDidMount
fires the first time a page is displayed, but if you navigate away from the page Ionic might keep the page around in the DOM, and a subsequent visit to the page might not call componentDidMount
again. This scenario is the main reason the Ionic lifecycle methods exist, to still give you a way to call logic when views enter and exit when the native framework's events might not fire.
#
Guidance for Each LifeCycle MethodBelow are some tips on uses cases for each of the life cycle events.
ionViewWillEnter
- SinceionViewWillEnter
is called every time the view is navigated to (regardless if initialized or not), it's a good method to load data from services.ionViewDidEnter
- If you see performance problems from usingionViewWillEnter
when loading data, you can do your data calls inionViewDidEnter
instead. This event won't fire until after the page is visible to the user, however, so you might want to use either a loading indicator or a skeleton screen, so content doesn't flash in un-naturally after the transition is complete.ionViewWillLeave
- Can be used for cleanup, like unsubscribing from data sources. SincecomponentWillUnmount
might not fire when you navigate from the current page, put your cleanup code here if you don't want it active while the screen is not in view.ionViewDidLeave
- When this event fires, you know the new page has fully transitioned in, so any logic you might not normally do when the view is visible can go here.