瀏覽代碼

Fixed a typo. (#3704)

Changed "assums" to "assumes".
Blake Barrett 6 年之前
父節點
當前提交
664a701fe8
共有 1 個檔案被更改,包括 1 行新增1 行删除
  1. 1
    1
      docs/android-specific-use-cases.md

+ 1
- 1
docs/android-specific-use-cases.md 查看文件

@@ -308,7 +308,7 @@ To disable the cross-fade animation, set `animated: false` when pushing the seco
308 308
 ## Compatibility with HeadlessJs
309 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 313
 ```js
314 314
 import {Navigation, NativeEventsReceiver} from 'react-native-navigation';