Skip to content

Commit

Permalink
Fixed a typo. (#3704)
Browse files Browse the repository at this point in the history
Changed "assums" to "assumes".
  • Loading branch information
BlakeBarrett authored and guyca committed Aug 9, 2018
1 parent 2c0fa0e commit 664a701
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/android-specific-use-cases.md
Expand Up @@ -308,7 +308,7 @@ To disable the cross-fade animation, set `animated: false` when pushing the seco
## Compatibility with HeadlessJs
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.

`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.
`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.

```js
import {Navigation, NativeEventsReceiver} from 'react-native-navigation';
Expand Down

0 comments on commit 664a701

Please sign in to comment.