You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/appstate.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do
20
20
21
21
## Basic Usage
22
22
23
-
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.
23
+
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.
24
+
25
+
:::info
26
+
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
27
+
:::
24
28
25
29
```SnackPlayer name=AppState%20Example
26
30
import React, {useRef, useState, useEffect} from 'react';
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.
77
+
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.
Copy file name to clipboardExpand all lines: website/versioned_docs/version-0.77/appstate.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do
20
20
21
21
## Basic Usage
22
22
23
-
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.
23
+
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.
24
+
25
+
:::info
26
+
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
27
+
:::
24
28
25
29
```SnackPlayer name=AppState%20Example
26
30
import React, {useRef, useState, useEffect} from 'react';
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.
77
+
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.
Copy file name to clipboardExpand all lines: website/versioned_docs/version-0.78/appstate.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do
20
20
21
21
## Basic Usage
22
22
23
-
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.
23
+
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.
24
+
25
+
:::info
26
+
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
27
+
:::
24
28
25
29
```SnackPlayer name=AppState%20Example
26
30
import React, {useRef, useState, useEffect} from 'react';
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.
77
+
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.
Copy file name to clipboardExpand all lines: website/versioned_docs/version-0.79/appstate.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do
20
20
21
21
## Basic Usage
22
22
23
-
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.
23
+
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.
24
+
25
+
:::info
26
+
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
27
+
:::
24
28
25
29
```SnackPlayer name=AppState%20Example
26
30
import React, {useRef, useState, useEffect} from 'react';
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.
77
+
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.
Copy file name to clipboardExpand all lines: website/versioned_docs/version-0.80/appstate.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do
20
20
21
21
## Basic Usage
22
22
23
-
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.
23
+
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.
24
+
25
+
:::info
26
+
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
27
+
:::
24
28
25
29
```SnackPlayer name=AppState%20Example
26
30
import React, {useRef, useState, useEffect} from 'react';
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.
77
+
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.
Copy file name to clipboardExpand all lines: website/versioned_docs/version-0.81/appstate.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do
20
20
21
21
## Basic Usage
22
22
23
-
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.
23
+
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.
24
+
25
+
:::info
26
+
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
27
+
:::
24
28
25
29
```SnackPlayer name=AppState%20Example
26
30
import React, {useRef, useState, useEffect} from 'react';
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.
77
+
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.
Copy file name to clipboardExpand all lines: website/versioned_docs/version-0.82/appstate.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do
20
20
21
21
## Basic Usage
22
22
23
-
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.
23
+
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.
24
+
25
+
:::info
26
+
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
27
+
:::
24
28
25
29
```SnackPlayer name=AppState%20Example
26
30
import React, {useRef, useState, useEffect} from 'react';
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.
77
+
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.
Copy file name to clipboardExpand all lines: website/versioned_docs/version-0.83/appstate.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,11 @@ For more information, see [Apple's documentation](https://developer.apple.com/do
20
20
21
21
## Basic Usage
22
22
23
-
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.
23
+
To see the current state, you can check `AppState.currentState`, which will be kept up-to-date.
24
+
25
+
:::info
26
+
If you are using the legacy architecture, `currentState` will be `null` at launch until it is retrieved asynchronously from the native side.
27
+
:::
24
28
25
29
```SnackPlayer name=AppState%20Example
26
30
import React, {useRef, useState, useEffect} from 'react';
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.
77
+
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.
0 commit comments