Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/appstate.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do

## Basic Usage

To see the current state, you can check `AppState.currentState`, which will be kept up-to-date. However, `currentState` will be null at launch while `AppState` retrieves it over the bridge.
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.

:::info
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
:::

```SnackPlayer name=AppState%20Example
import React, {useRef, useState, useEffect} from 'react';
Expand Down Expand Up @@ -70,7 +74,7 @@ const styles = StyleSheet.create({
export default AppStateExample;
```

This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state, and the null state will happen only momentarily. If you want to experiment with the code we recommend to use your own device instead of embedded preview.
This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state. If you want to experiment with the code we recommend to use your own device instead of embedded preview.

---

Expand Down
8 changes: 6 additions & 2 deletions website/versioned_docs/version-0.77/appstate.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do

## Basic Usage

To see the current state, you can check `AppState.currentState`, which will be kept up-to-date. However, `currentState` will be null at launch while `AppState` retrieves it over the bridge.
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.

:::info
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
:::

```SnackPlayer name=AppState%20Example
import React, {useRef, useState, useEffect} from 'react';
Expand Down Expand Up @@ -70,7 +74,7 @@ const styles = StyleSheet.create({
export default AppStateExample;
```

This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state, and the null state will happen only momentarily. If you want to experiment with the code we recommend to use your own device instead of embedded preview.
This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state. If you want to experiment with the code we recommend to use your own device instead of embedded preview.

---

Expand Down
8 changes: 6 additions & 2 deletions website/versioned_docs/version-0.78/appstate.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do

## Basic Usage

To see the current state, you can check `AppState.currentState`, which will be kept up-to-date. However, `currentState` will be null at launch while `AppState` retrieves it over the bridge.
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.

:::info
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
:::

```SnackPlayer name=AppState%20Example
import React, {useRef, useState, useEffect} from 'react';
Expand Down Expand Up @@ -70,7 +74,7 @@ const styles = StyleSheet.create({
export default AppStateExample;
```

This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state, and the null state will happen only momentarily. If you want to experiment with the code we recommend to use your own device instead of embedded preview.
This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state. If you want to experiment with the code we recommend to use your own device instead of embedded preview.

---

Expand Down
8 changes: 6 additions & 2 deletions website/versioned_docs/version-0.79/appstate.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do

## Basic Usage

To see the current state, you can check `AppState.currentState`, which will be kept up-to-date. However, `currentState` will be null at launch while `AppState` retrieves it over the bridge.
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.

:::info
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
:::

```SnackPlayer name=AppState%20Example
import React, {useRef, useState, useEffect} from 'react';
Expand Down Expand Up @@ -70,7 +74,7 @@ const styles = StyleSheet.create({
export default AppStateExample;
```

This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state, and the null state will happen only momentarily. If you want to experiment with the code we recommend to use your own device instead of embedded preview.
This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state. If you want to experiment with the code we recommend to use your own device instead of embedded preview.

---

Expand Down
8 changes: 6 additions & 2 deletions website/versioned_docs/version-0.80/appstate.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do

## Basic Usage

To see the current state, you can check `AppState.currentState`, which will be kept up-to-date. However, `currentState` will be null at launch while `AppState` retrieves it over the bridge.
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.

:::info
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
:::

```SnackPlayer name=AppState%20Example
import React, {useRef, useState, useEffect} from 'react';
Expand Down Expand Up @@ -70,7 +74,7 @@ const styles = StyleSheet.create({
export default AppStateExample;
```

This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state, and the null state will happen only momentarily. If you want to experiment with the code we recommend to use your own device instead of embedded preview.
This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state. If you want to experiment with the code we recommend to use your own device instead of embedded preview.

---

Expand Down
8 changes: 6 additions & 2 deletions website/versioned_docs/version-0.81/appstate.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do

## Basic Usage

To see the current state, you can check `AppState.currentState`, which will be kept up-to-date. However, `currentState` will be null at launch while `AppState` retrieves it over the bridge.
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.

:::info
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
:::

```SnackPlayer name=AppState%20Example
import React, {useRef, useState, useEffect} from 'react';
Expand Down Expand Up @@ -70,7 +74,7 @@ const styles = StyleSheet.create({
export default AppStateExample;
```

This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state, and the null state will happen only momentarily. If you want to experiment with the code we recommend to use your own device instead of embedded preview.
This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state. If you want to experiment with the code we recommend to use your own device instead of embedded preview.

---

Expand Down
8 changes: 6 additions & 2 deletions website/versioned_docs/version-0.82/appstate.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do

## Basic Usage

To see the current state, you can check `AppState.currentState`, which will be kept up-to-date. However, `currentState` will be null at launch while `AppState` retrieves it over the bridge.
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.

:::info
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
:::

```SnackPlayer name=AppState%20Example
import React, {useRef, useState, useEffect} from 'react';
Expand Down Expand Up @@ -70,7 +74,7 @@ const styles = StyleSheet.create({
export default AppStateExample;
```

This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state, and the null state will happen only momentarily. If you want to experiment with the code we recommend to use your own device instead of embedded preview.
This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state. If you want to experiment with the code we recommend to use your own device instead of embedded preview.

---

Expand Down
8 changes: 6 additions & 2 deletions website/versioned_docs/version-0.83/appstate.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do

## Basic Usage

To see the current state, you can check `AppState.currentState`, which will be kept up-to-date. However, `currentState` will be null at launch while `AppState` retrieves it over the bridge.
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.

:::info
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
:::

```SnackPlayer name=AppState%20Example
import React, {useRef, useState, useEffect} from 'react';
Expand Down Expand Up @@ -70,7 +74,7 @@ const styles = StyleSheet.create({
export default AppStateExample;
```

This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state, and the null state will happen only momentarily. If you want to experiment with the code we recommend to use your own device instead of embedded preview.
This example will only ever appear to say "Current state is: active" because the app is only visible to the user when in the `active` state. If you want to experiment with the code we recommend to use your own device instead of embedded preview.

---

Expand Down