-
Notifications
You must be signed in to change notification settings - Fork 17
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
TypeError: _reactNativeNavigation.Navigation.startSingleScreenApp is not a function. #10
Comments
Did anyone figure this out? I have the same issue. |
@trialsNow, when I was toying with the adapter it was completely broken, so I did full scale migration to v2 and it mostly works as expected now. |
hmm .. i am still facing the same issue even with latest native navigation.. Can you help me? "dependencies": { App.js Navigation.registerComponent('example.HomeScreen', () => IntroSlider); IntroSlider.js const styles = StyleSheet.create({ const slides = [ class IntroSlider extends Component { onDone = () => { onSkip = () => { render() { export default IntroSlider; AppDelegate
Error: |
@trialsNow, there is really no such a function in RNN2. Docs. |
The docs link is broken. I am confused now, the startsinglescreenapp and starttabbasedapp was available in v1. Is it not anymore? |
oh got it.. its setroot now .. thank you so much @terreb |
@trialsNow did you find any solution to this? please post your solution I am also getting the same issue. |
@anupgupta-arg I was using the v1 methods. The starttabbased and startsingleapp methods are obsolete.. here is what needs to be done. However I must admit, I loved v1 more. V2 seems complicated to understand for a beginner. I still cant host a good tab based app with v2. With V1 I did it in an hour of looking at it. |
I've run into a ton of deprecated, renamed, or otherwise changed function names, constructors, and other various things while using this and other RN libraries. I highly suggest that at some point it becomes standard practice to throw meaningful error messages that indicate when a function is or is about to be deprecated, instead of simply dropping them cold and leaving developers with no clue as to what changed or why. Yes, we can read documentation, however when there are multiple sets of documentation, multiple versions of things, and a resulting plethora of conflicting examples, this can get very confusing when the API changes drastically and produces no meaningful error messages or other clues. Just a suggestion. |
omg, finally :)) the link is exactly what i'm looking for. I'm following a tutorial teaching RN with RNN v1, and it just drives me crazy with apis from v1. whatever, tks for sharing the link |
I've been using RNN v1. Due to some issues that won't be addressed since it's not getting support any more I'm moving to RNN v2. To see if if it works fine before rewriting the code to new API I would like to try it with the adapter. I followed the instructions to set up the ios project. When I run the app I get
TypeError: _reactNativeNavigation.Navigation.startSingleScreenApp is not a function
Here is my App.js:
The text was updated successfully, but these errors were encountered: