@otaupdate/react-native 1.0.3 → 1.0.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +20 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -22,6 +22,26 @@ rollback-on-failure; JS handles the update check and the app-facing API.
|
|
|
22
22
|
npm install @otaupdate/react-native
|
|
23
23
|
```
|
|
24
24
|
|
|
25
|
+
> **Bare React Native on Android — pin your version to match your RN version.**
|
|
26
|
+
> `npm install` with no version pin gets you the latest (currently 1.0.5).
|
|
27
|
+
> That version relies on an internal React Native API whose shape changed
|
|
28
|
+
> between RN releases — it requires **RN 0.80+**. If your app is on an
|
|
29
|
+
> **older RN version (0.7x)**, pin `@otaupdate/react-native@1.0.4` instead:
|
|
30
|
+
>
|
|
31
|
+
> ```bash
|
|
32
|
+
> npm install @otaupdate/react-native@1.0.4 # RN 0.7x
|
|
33
|
+
> npm install @otaupdate/react-native@1.0.5 # RN 0.80+ (or just @otaupdate/react-native)
|
|
34
|
+
> ```
|
|
35
|
+
>
|
|
36
|
+
> Both versions are fully functional and behave identically from the JS API
|
|
37
|
+
> you call (`sync`, `checkForUpdate`, `withOtaUpdate`, etc. — none of that
|
|
38
|
+
> changes). The only difference is *how* Android applies a mandatory/resume
|
|
39
|
+
> install: 1.0.4 restarts the process (a brief visible flash during the
|
|
40
|
+
> switch); 1.0.5 swaps the bundle in place with no restart and no flash, the
|
|
41
|
+
> same way Expo's own update mechanism does, but that technique only exists
|
|
42
|
+
> on newer RN. Expo and iOS are unaffected by any of this — both already
|
|
43
|
+
> update seamlessly regardless of which SDK version you're on.
|
|
44
|
+
|
|
25
45
|
### Bare React Native
|
|
26
46
|
|
|
27
47
|
**iOS**
|