Calling the same modal component twice throws error on .dismiss()

[crockpotveggies]

Here's what my routing tree looks at its simplest:

<Router>
  <Route name="errorModal" type="modal" component={ErrorModal}/>
  <Route name="mainScreen" initial={!needSignIn}>
    .. tab bar stuff ...
  </Route>
  <Route name="Login" initial={needSignIn} component={LoginScreen}/>
</Router>

Whenever an error happens within the app, I usually call Actions.errorModal({message: 'bad'}). However, during testing I noticed if I call that modal, then Actions.dismiss() and immediately afterwards call the error modal again then Actions.dismiss() a second time, the modal will not dismiss. Then, if I try to navigate to another part of the app, the app will crash with the following error:

It looks like there's an error with resetting the route stack when calling dismiss() and the router can't handle a second modal being called immediately thereafter (with no other navigation). Is this a bug or am I not properly using modals?

[aksonov]

It is wrong use case - modal should not be called twice, prevent it from your code.

[crockpotveggies]

@aksonov can you elaborate a little more? What if there are two errors in a row (for instance, we start having API troubles and multiple requests fail?)

Thanks!

[aksonov]

Should be fixed for 3.0 release

[crockpotveggies]

Thanks for the update. Anything I can do to help with the release?

[aksonov]

You may check how it works. I didn't test it with several popups yet.

[aksonov]

And 3.0 is not backward compatible...

[crockpotveggies]

Yep just saw the breaking changes. Let me put together a fork of our mobile repo later tonight and I'll start testing it out :)

[aksonov]

I'm closing it for now