-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Unable to navigate to Scene with Actions.key #2452
Comments
I am also getting this error. Can't navigate to another scene and no error is displayed. RN 0.48.3, react-native-router-flux 4.0.0-beta.21 |
|
Did you not read my bug report. I already said i tried all variations of
function call in onPress. None of them are working. This bug should not be
closed
…On Wed, Oct 4, 2017 at 7:04 AM Miguel ***@***.***> wrote:
Closed #2452
<#2452>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2452 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AExqBzCx-Iob0GmrHAgofYBrCO0rfIsmks5so5BkgaJpZM4Pq_EX>
.
|
you said you tried {ACTIONS.LoginScreen()}, that isn't the same as {() => Actions.LoginScreen()} |
"i have tried all permuatations of the call in bold (
{ACTIONS.LoginScreen}, {ACTIONS.LoginScreen()} etc"
So yes your suggestion has been tried and it does not work.
…On Wed, Oct 4, 2017 at 7:43 AM Miguel ***@***.***> wrote:
you said you tried {ACTIONS.LoginScreen()}, that isn't the same as {() =>
Actions.LoginScreen()}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2452 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AExqB29BEl7KRIO-9msCWom9apoCUsxcks5so5mtgaJpZM4Pq_EX>
.
|
What Scene are you at trying to navigate to |
I have updated your description of the problem to better explain your situation, please review it when you have a moment. |
I also get this issue. Before it worked fine on React-native-router-flux 3.38. I then updated to the latest version of react-native-router-flux and now as mentioned in this open issue, I can't change scenes using ACTIONS.KEY. I tried with RN 0.48.3 and 0.48.4 and I get the same issue |
I've been facing a similar issue. <Router>
<Scene key="root" hideNavBar>
{/* Authentication Bucket */}
<Scene key="auth" >
<Scene key="login" component={LoginForm} title="ManagerLogin" initial />
</Scene>
{/* Main Bucket */}
<Scene key="main" >
<Scene
rightTitle=" Add"
onRight={() => Actions.AddEmployee()}
key="employeeList"
component={EmployeeList}
title="Employee List"
initial
/>
<Scene key="addEmloyee" component={AddEmployee} title="Add Employee" />
</Scene>
{/* Test Bucket */}
<Scene key="moo" >
<Scene key="add" component={AddEmployee} title="Add Employee" />
<Scene key="emp" component={EmployeeList} title="Employee" />
</Scene>
</Scene>
</Router> in the above code when I click on Case2: Case 2.1: Case 3: P.S. i only get an error when i add Actions.key to onRight whereas there's simply no response in other cases. |
I am having the same problem. Happened when I tried to move to the beta since 3.38 does not work on RN 0.49 |
Please read docs for v4 - you should not have both |
hey @aksonov that doesn't solve my issue. I don't have component defined in my container. |
Do you mean wrongly typed Actions.AddEmployee() ? |
AddEmployee is the component name while |
You tried another action staring with uppercase
… 10 окт. 2017 г., в 19:18, Karan Wadhwa ***@***.***> написал(а):
AddEmployee is the component name while addEmployee is the key so Actions.addEmployee() should work but it doesnt.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
no i didnt. please refer to this
<Router>
<Scene key="root" hideNavBar>
{/* Authentication Bucket */}
<Scene key="auth" >
<Scene key="login" component={LoginForm} title="ManagerLogin" initial />
</Scene>
{/* Main Bucket */}
<Scene key="main" >
<Scene
rightTitle=" Add"
onRight={() => Actions.AddEmployee()}
key="employeeList"
component={EmployeeList}
title="Employee List"
initial
/>
<Scene key="addEmloyee" component={AddEmployee} title="Add Employee" />
</Scene>
{/* Test Bucket */}
<Scene key="moo" >
<Scene key="add" component={AddEmployee} title="Add Employee" />
<Scene key="emp" component={EmployeeList} title="Employee" />
</Scene>
</Scene>
</Router> in the above code when I click on Case2: Case 2.1: Case 3: P.S. i only get an error when i add Actions.key to onRight whereas there's simply no response in other cases. |
I also get the same issue... when I run the "demo app", it works. But when I import to my working (ejected) app, it doesn't. Any hints? Thanks! |
@karanwadhwa did you solve this? |
Yes, I have just solved it. Thanks!
Em 5 de dez de 2017 18:16, "Jeovany" <notifications@github.com> escreveu:
… @karanwadhwa <https://github.com/karanwadhwa> did you solved this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2452 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF_I2LLdXlKj4VUpcLOWNGnRx4uWdlXqks5s9c7igaJpZM4Pq_EX>
.
|
Running into exactly same issue . It ran smoothly for me earlier with the same code but when i created a new project with the same code, it stopped working on some places . Please do help. |
Can you please tell me how to solve this? |
Any status on this issue? |
This is an issue with the latest update of the library. Trying adding both the scenes under the same parent scene. If both of them exist under different scenes. Try : Actions.parentKey; Actions.scene |
It worked . . Thanks lot @gagantaneja |
use |
eu não conseguir chamar a função do meu botão |
thank a lot |
Version
Tell us which versions you are using:
Expected behaviour
expect ACTIONS.KEY to take me to the necessary scene.
Actual behaviour
nothing happens. no errors i just stay stuck on the same scene.
Steps to reproduce
and here is where i am calling it
i have tried these permutations of the
onPress
:{() => Actions.LoginScreen}
{() => Actions.LoginScreen()}
{Actions.LoginScreen}
So thats not the problem. one gentleman solved this by going to v3. thats not working for me
The text was updated successfully, but these errors were encountered: