Browse Source

Fixed a typo. (#3704)

Changed "assums" to "assumes".
Blake Barrett 6 years ago
parent
commit
664a701fe8
1 changed files with 1 additions and 1 deletions
  1. 1
    1
      docs/android-specific-use-cases.md

+ 1
- 1
docs/android-specific-use-cases.md View File

308
 ## Compatibility with HeadlessJs
308
 ## Compatibility with HeadlessJs
309
 In most cases, `Navigation.startSingleScreenApp()` or `Navigation.startTabBasedApp` are called from global context. If the bundle is parsed when the app is not running, this will result in the app opening even though the developer had no intent to open the app.
309
 In most cases, `Navigation.startSingleScreenApp()` or `Navigation.startTabBasedApp` are called from global context. If the bundle is parsed when the app is not running, this will result in the app opening even though the developer had no intent to open the app.
310
 
310
 
311
-`Navigation.startSingleScreenApp()` or `Navigation.startTabBasedApp` are called from global context since RNN assums react context isn't created when the app is launched. When a background task completes, react context is put into a **paused state** and not destroyed. Therefore we should also handle the use case where our app is opened when react context is created , and the bundle has already been parsed. We do that by listening to `RNN.AppLaunched` event.
311
+`Navigation.startSingleScreenApp()` or `Navigation.startTabBasedApp` are called from global context since RNN assumes react context isn't created when the app is launched. When a background task completes, react context is put into a **paused state** and not destroyed. Therefore we should also handle the use case where our app is opened when react context is created , and the bundle has already been parsed. We do that by listening to `RNN.AppLaunched` event.
312
 
312
 
313
 ```js
313
 ```js
314
 import {Navigation, NativeEventsReceiver} from 'react-native-navigation';
314
 import {Navigation, NativeEventsReceiver} from 'react-native-navigation';