Skip to content
This repository was archived by the owner on May 20, 2025. It is now read-only.

Commit dd6e76f

Browse files
committed
Adding docs for dis/allowRestart
1 parent 006224a commit dd6e76f

File tree

1 file changed

+71
-0
lines changed

1 file changed

+71
-0
lines changed

README.md

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -450,8 +450,12 @@ The following sections describe the shape and behavior of these APIs in detail:
450450

451451
When you require `react-native-code-push`, the module object provides the following top-level methods:
452452

453+
* [allowRestart](#codepushallowrestart): Re-allows programmatic restarts to occur as a result of an update being installed, and optionally, immediately restarts the app if a pending update had attempted to restart the app while restarts were disallowed. This is an advanced API and is only neccessary if your app explicitly disallowed restarts via the `disallowRestart` method.
454+
453455
* [checkForUpdate](#codepushcheckforupdate): Asks the CodePush service whether the configured app deployment has an update available.
454456

457+
* [disallowRestart](#codepushdisallowrestart): Temporarily disallows any programmatic restarts to occur as a result of a CodePush update being installed. This is an advanced API, and is useful when a component within your app (e.g. an onboarding wizard) needs to ensure that no end-user interruptions can occur during its lifetime.
458+
455459
* [getCurrentPackage](#codepushgetcurrentpackage): Retrieves the metadata about the currently installed update (e.g. description, installation time, size). *NOTE: As of `v1.10.3-beta` of the CodePush module, this method is deprecated in favor of [`getUpdateMetadata`](#codepushgetupdatemetadata)*.
456460

457461
* [getUpdateMetadata](#codepushgetupdatemetadata): Retrieves the metadata for an installed update (e.g. description, mandatory).
@@ -462,6 +466,30 @@ When you require `react-native-code-push`, the module object provides the follow
462466

463467
* [sync](#codepushsync): Allows checking for an update, downloading it and installing it, all with a single call. Unless you need custom UI and/or behavior, we recommend most developers to use this method when integrating CodePush into their apps
464468

469+
#### codePush.allowRestart
470+
471+
```javascript
472+
codePush.allowRestart(): void;
473+
```
474+
475+
Re-allows programmatic restarts to occur, that would have otherwise been rejected due to a previous call to `disallowRestart`. If `disallowRestart` was never called in the first place, then calling this method will simply result in a no-op.
476+
477+
If a pending CodePush update is currently pending, which attempted to restart the app, but was blocked due to `disallowRestart` having been called, then calling `allowRestart` will result in an immediate restart. This allows the update to be applied as soon as possible, without interrupting the end user during critical workflows (e.g. an onboarding wizard).
478+
479+
For example, calling `allowRestart` would trigger an immediate restart if either of the three scenarios mentioned in [disallowRestart](#codepushdisallowrestart) occured after `disallowRestart` was called. However, calling `allowRestart` wouldn't trigger a restart if the following were true:
480+
481+
1. No CodePush updates were installed since the last time `disallowRestart` was called, and therefore, there isn't any need to restart anyways.
482+
483+
2. There is currently a pending CodePush update, but it was installed via `InstallMode.ON_NEXT_RESTART`, and therefore, doesn't require a programmatic restart.
484+
485+
3. There is currently a pending CodePush update, but it was installed via `InstallMode.ON_NEXT_RESUME` and the app hasn't been put into the background yet, and therefore, there isn't a need to programmatically restart yet.
486+
487+
3. No calls to `restartApp` were made since the last time `disallowRestart` was called.
488+
489+
This behavior ensures that no restarts will be triggered as a result of calling `reallowRestart` unless one was explictly requested during the disallowed period.
490+
491+
See [disallowRestart](#codepushdisallowrestart) for an example of how this method can be used.
492+
465493
#### codePush.checkForUpdate
466494
467495
```javascript
@@ -493,6 +521,49 @@ codePush.checkForUpdate()
493521
});
494522
```
495523

524+
#### codePush.disallowRestart
525+
526+
```javascript
527+
codePush.disallowRestart(): void;
528+
```
529+
530+
Temporarily disallows programmatic restarts to occur as a result of either of following scenarios:
531+
532+
1. A CodePush update is installed using `InstallMode.IMMEDIATE`
533+
2. A CodePush update is installed using `InstallMode.ON_NEXT_RESUME` and the app is resumed from the background (optionally being throttled by the `minimumBackgroundDuration` property)
534+
3. The `restartApp` method was called
535+
536+
*NOTE: #1 and #2 effectively work by calling `restartApp` for you, so you can think of `disallowRestart` as blocking any call to `restartApp`, regardless if your app calls it directly or indirectly.*
537+
538+
After calling this method, any calls to `sync` would still be allowed to check for an update, download it and install it, but an attempt to restart the app would be queued until `reallowRestart` is called. This way, the restart request is captured and can be "flushed" whenever you want to allow it to occur.
539+
540+
This is an advanced API, and is primarily useful when individual components within your app (e.g. an onboarding wizard) need to ensure that no end-user interruptions can occur during their lifetime, while continuing to allow the app to keep syncing with the CodePush server at its own pace and using whatever install modes are appropriate. This has the benefit of allowing the app to discover and download available updates as soon as possible, while also preventing any disruptions during key end-user experiences.
541+
542+
As an alternative, you could also choose to simply use `InstallMode.ON_NEXT_RESTART` whenever calling `sync` (which will never attempt to programmatically restart the app), and then explicity calling `restartApp` at points in your app that you know it is "safe" to do so. `disallowRestart` provides an alternative approach to this when the code that sychronizes with the CodePush server is seperate from the code/comopents that want to enforce a no-restart policy.
543+
544+
Example Usage:
545+
546+
```javascript
547+
class OnboardingWizard extends Component {
548+
...
549+
550+
componentWillMount() {
551+
// Ensure that any CodePush updates which are
552+
// synchronized in the background can't trigger
553+
// a restart while this component is mounted.
554+
codePush.disallowRestart();
555+
}
556+
557+
componentWillUnmount() {
558+
// Reallow restarts, and optionally trigger
559+
// a restart if one was currently pending.
560+
codePush.allowRestart();
561+
}
562+
563+
...
564+
}
565+
```
566+
496567
#### codePush.getCurrentPackage
497568

498569
*NOTE: This method is considered deprecated as of `v1.10.3-beta` of the CodePush module. If you're running this version (or newer), we would recommend using the [`codePush.getUpdateMetadata`](#codepushgetupdatemetadata) instead, since it has more predictable behavior.*

0 commit comments

Comments
 (0)