React-native-navigation: Lifecycle events

[beast]

As @DanielZlotin mentioned in issue https://github.com/wix/react-native-navigation/issues/74
Lifecycle events are not implemented yet but it's a critical feature that is being looked into. Could I know the timeline for this? One of the challenges I have is when architecting the Android app knowing there will be a lot of invisible react components. (And duplicates if navigated through push.) If I am not being careful with the lifecycle events I could potentially end up with bad data and other side effects. Thanks.

[DanielZlotin]

tl;dr The best estimate I can give you right now is by the end of next month.

We are in the process of a complete redesign of the project and unification of controllers and navigation, and the lifecycle feature is our top priority right after that. This project is used in our production environment, so you get somewhat slower development, but the upside is you can expect a stable, battle tested and solid code, once we mature it from its "proof of concept" stage.

[beast]

@DanielZlotin Thanks for the prompt response. That is a great news and we are going all out with this package with our iOS app at the moment. Can't wait until the Android version really catches up. Great work!

[agumack]

@DanielZlotin, @guyca i have some apps using 'react-native-navigation' on Appstore, and waiting this feature for android.
I found a temporarily solution, too
Can you suggest us?
Thanks you so much :)

[agumack]

woo, I detect seem all screen called are filename same "index.js"

Ex: Tab1floder/index.js (tab1screen code) => It called will StartApp but change Tab1folder/Tab1.js => run correct.

[DanielMaly]

@DanielZlotin Any updates on this? Is it planned for v2.1?

[adamski]

Hi guys, any updates on lifecycle events?

[DanielZlotin]

WIP, planned for 2.0.0