docs: mark RN 0.82-0.83 supported

Fixes #17

Author: Minishlink

README.md

@@ -103,7 +103,7 @@ See the [corresponding steps](./docs/migrating-to-v10.md).
 We try our best to maintain backwards compatibility of our plugin with previous versions of React Native, but due to the nature of the platform, and the existence of breaking changes between releases, it is possible that you need to use a specific version of the CodePush plugin in order to support the exact version of React Native you are using. The following table outlines which CodePush plugin versions officially support the respective React Native versions:
 
 | React Native version(s) | Android         | iOS  | Old arch | New arch | Supporting CodePush version(s) |
-| ----------------------- | --------------- | ---- | -------- | -------- | ------------------------------ |
+|-------------------------| --------------- | ---- | -------- | -------- | ------------------------------ |
 | <0.59                   | -               | -    | ✅       | ❌       | **Unsupported**                |
 | v0.59                   | 4.1+ (TLS 1.2+) | 7    | ✅       | ❌       | v5.7.1                         |
 | v0.60-v0.61             | 4.1+ (TLS 1.2+) | 7    | ✅       | ❌       | v6.3.1                         |
@@ -112,7 +112,7 @@ We try our best to maintain backwards compatibility of our plugin with previous
 | v0.71-v0.79             | 4.1+ (TLS 1.2+) | 9    | ✅       | ❌       | v8.3.2                         |
 | v0.71-v0.79             | 4.1+ (TLS 1.2+) | 15.5 | ✅       | ❌       | v9.0.2                         |
 | v0.71-v0.80             | 4.1+ (TLS 1.2+) | 15.5 | ✅       | ❌       | v10+                           |
-| v0.74-v0.81             | 4.1+ (TLS 1.2+) | 15.5 | ✅       | ✅       | v11+                           |
+| v0.74-v0.83             | 4.1+ (TLS 1.2+) | 15.5 | ✅       | ✅       | v11+                           |
 
 We work hard to respond to new RN releases, but they do occasionally break us. We will update this chart with each RN release, so that users can check to see what our "official" support is.
 

docs/code-signing.md

@@ -54,7 +54,7 @@ Add record in `Info.plist` with name `CodePushSigningPublicKey` and string value
     <!-- ...other configs... -->
 
     <key>CodePushSigningPublicKey</key>
-        <string>-----BEGIN PUBLIC KEY-----
+    <string>-----BEGIN PUBLIC KEY-----
 MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANkWYydPuyOumR/sn2agNBVDnzyRpM16NAUpYPGxNgjSEp0etkDNgzzdzyvyl+OsAGBYF3jCxYOXozum+uV5hQECAwEAAQ==
 -----END PUBLIC KEY-----</string>
 

docs/setup-android.md

@@ -14,7 +14,31 @@
 
 2. Update the `MainApplication` file to use CodePush via the following changes:
 
-   If your MainApplication is a Kotlin file, update the `MainApplication.kt`
+   If your MainApplication is a Kotlin file on RN >= 0.82, update the `MainApplication.kt`:
+
+   ```kotlin
+   ...
+   // 1. Import the plugin class.
+   import com.appzung.codepush.react.CodePush
+
+   class MainApplication : Application(), ReactApplication {
+    
+   override val reactHost: ReactHost by lazy {
+       getDefaultReactHost(
+           context = applicationContext,
+           packageList =
+             PackageList(this).packages.apply {
+               // Packages that cannot be autolinked yet can be added manually here, for example:
+               // add(MyReactNativePackage())
+           },
+           // 2. Override the getJSBundleFile method in order to let
+           // the CodePush runtime determine where to get the JS
+           // bundle location from on each app start (after packageList)
+           jsBundleFilePath = CodePush.getJSBundleFile(),
+           ...
+   ```
+
+   If your MainApplication is a Kotlin file on RN < 0.82, update the `MainApplication.kt`:
 
    ```kotlin
    ...
@@ -95,7 +119,7 @@
    ```xml
     <resources>
         <string name="app_name">AppName</string>
-        <string moduleConfig="true" name="CodePushReleaseChannelPublicId">ReleaseChannelPublicId</string>
+        <string name="CodePushReleaseChannelPublicId">ReleaseChannelPublicId</string>
     </resources>
    ```
 

docs/setup-ios.md

@@ -4,38 +4,38 @@
 
 ### Plugin Installation and Configuration
 
-1. Run `cd ios && pod install && cd ..` to install all the necessary CocoaPods dependencies.
+1. Run `cd ios && pod install && cd ..` to install all the necessary CocoaPods dependencies. You may have to change the `Podfile`'s min iOS version to 15.5 (`platform :ios, '15.5'`).
 
-2. Open up the `AppDelegate.m`/`AppDelegate.swift` file, and add an import statement for the CodePush headers:
-
-   ```objective-c
-   #import <CodePush/CodePush.h>
-   ```
+2. Open up the `AppDelegate.swift`/`AppDelegate.m` file, and add an import statement for the CodePush headers:
 
    ```swift
    import CodePush
    ```
 
-3. Find the following line of code, which sets the source URL for bridge for production releases:
-
    ```objective-c
-   return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
+   #import <CodePush/CodePush.h>
    ```
 
+3. Find the following line of code, which sets the source URL for bridge for production releases:
+
    ```swift
    Bundle.main.url(forResource: "main", withExtension: "jsbundle")
    ```
 
-4. Replace it with this line:
-
    ```objective-c
-   return [CodePush bundleURL];
+   return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
    ```
 
+4. Replace it with this line:
+
    ```swift
    CodePush.bundleURL()
    ```
 
+   ```objective-c
+   return [CodePush bundleURL];
+   ```
+
    This change configures your app to always load the most recent version of your app's JS bundle. On the first launch, this will correspond to the file that was compiled with the app. However, after an update has been pushed via CodePush, this will return the location of the most recently installed update.
 
    _NOTE: The `bundleURL` method assumes your app's JS bundle is named `main.jsbundle`. If you have configured your app to use a different file name, simply call the `bundleURLForResource:` method (which assumes you're using the `.jsbundle` extension) or `bundleURLForResource:withExtension:` method instead, in order to overwrite that default behavior_
@@ -44,6 +44,16 @@
 
    Your `sourceURLForBridge` method should look like this:
 
+   ```swift
+     override func bundleURL() -> URL? {
+   #if DEBUG
+       RCTBundleURLProvider.sharedSettings().jsBundleURL(forBundleRoot: "index")
+   #else
+       CodePush.bundleURL()
+   #endif
+     }
+   ```
+
    ```objective-c
    - (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
    {
@@ -55,16 +65,6 @@
    }
    ```
 
-   ```swift
-     override func bundleURL() -> URL? {
-   #if DEBUG
-       RCTBundleURLProvider.sharedSettings().jsBundleURL(forBundleRoot: "index")
-   #else
-       CodePush.bundleURL()
-   #endif
-     }
-   ```
-
 5. Add the Release channel public ID to `Info.plist`:
 
    To let the CodePush runtime know which release channel it should query for updates against, open your app's `Info.plist` file and add a new entry named `CodePushReleaseChannelPublicId`, whose value is the public ID of the release channel you want to configure this app against. You can retrieve this value by running `appzung release-channels list` in the AppZung CLI and copying the value of the `Public ID` column.