GitBook: [master] 2 pages modified

Author: christianalfoni

SUMMARY.md

@@ -31,6 +31,7 @@
 ## Guides <a id="guides-1"></a>
 
 * [Connecting components](guides-1/connecting-components.md)
+* [Connecting to React Native](https://dev.to/brasilikum/how-to-setup-overmind-with-react-native-expo-optional-4mk5)
 * [Managing lists](guides-1/managing-lists.md)
 * [State first routing](guides-1/state-first-routing.md)
 * [Server Side Rendering](guides-1/server-side-rendering.md)

core/defining-state.md

@@ -387,7 +387,7 @@ You set an **initial** state and then you create a relationship between the diff
 export const login = async ({ state, effects }) => {
   return state.mode.authenticating(async () => {
     try {
-      const user = effects.api.getUser()
+      const user = await effects.api.getUser()
       return state.mode.authenticated(() => {
         state.user = user
       })
@@ -418,8 +418,8 @@ export const logout = async ({ state, effects }) => {
 {% hint style="warning" %}
 There are two important rules for predictable transitions:
 
-1. The transition should always **return**
-2. **Async** transitions should not **mutate** state
+1. The transition should always be **returned**
+2. A transition can either run **async** OR **mutate**, not both
 {% endhint %}
 
 What is important to realize here is that our logic is separated into **allowable** transitions. That means when we are waiting for the user on **line 4** and some other logic has changed the state to **unauthenticated** in the meantime, the user will not be set, as the **authenticated** transition is now not possible. This is what state machines do. They group logic into states that are allowed to run, preventing invalid logic to run.