Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

[V2] [iOS] RNN.componentDidAppear is not a supported event type for RNNEventEmitter #3703

Closed
jsmankoo opened this issue Aug 6, 2018 · 9 comments

Comments

@jsmankoo
Copy link

jsmankoo commented Aug 6, 2018

Issue Description

App fails to start.
screen shot 2018-08-06 at 4 23 20 pm

RNN.componentDidAppear is not a supported event type for RNNEventEmitter.
Supported events are: RNN.AppLaunched, RNN.CommandCompleted, RNN.BottomTabSelected, RNN.ComponentDidAppear, RNN.ComponentDidDisappear, RNN.NavigationButtonPressed, RNN.SearchBarUpdated, RNN.SearchBarCancelPressed, RNN.PreviewCompleted.

Steps to Reproduce / Code Snippets / Screenshots

  1. install v2.0.2459 (current latest)
  2. link libraries
  3. run app

currently I'm only able to use version v2.0.2404


Environment

  • React Native Navigation version: 2.0.2459
  • React Native version: 0.56.0
  • Platform(s) (iOS, Android, or both?): ios
  • Device info (Simulator/Device? OS version? Debug/Release?): Simulator iPhoneX iOS 11.4 Debug
@jsmankoo jsmankoo changed the title v2: RNN.componentDidAppear is not a supported event type for RNNEventEmitter [V2] [iOS] RNN.componentDidAppear is not a supported event type for RNNEventEmitter Aug 7, 2018
@zeucxb
Copy link

zeucxb commented Aug 22, 2018

Same

@jsmankoo
Copy link
Author

Can we get an update on this?

@WeiLiangTan
Copy link

WeiLiangTan commented Sep 25, 2018

@ue
Copy link

ue commented Sep 29, 2018

Did you use yarn @jsmankoo

@jsmankoo
Copy link
Author

jsmankoo commented Oct 1, 2018

yes @ue , we use yarn.

@ue
Copy link

ue commented Oct 1, 2018

@jsmankoo Can you try npm install instead of yarn. I hope it will fix it.

@jsmankoo
Copy link
Author

jsmankoo commented Oct 1, 2018

@ue I can confirm that removing node_modules and re-installing via npm install and not yarn install does fixes this. However I'm not sure whether that constitutes as the issue being "fixed".

@stale
Copy link

stale bot commented Nov 26, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you believe the issue is still relevant, please test on the latest Detox and report back. Thank you for your contributions.

@stale stale bot added the 🏚 stale label Nov 26, 2018
@stale
Copy link

stale bot commented Dec 3, 2018

The issue has been closed for inactivity.

@stale stale bot closed this as completed Dec 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants