@swyng/react-native-code-push 1.0.1 → 1.0.2

package/CLAUDE.md

@@ -4,7 +4,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Overview
 
-SwyngPush React Native (`@swyng/react-native-code-push`) is a native module that enables over-the-air updates for React Native apps. It consists of native implementations for iOS (Objective-C), Android (Java), and Windows (C++), unified through a JavaScript bridge layer. The server-side is hosted at swyngpush.site.
+SwyngPush React Native (`@swyng/react-native-code-push`) is a native module that enables over-the-air updates for React Native apps. It consists of native implementations for iOS (Objective-C), Android (Java), and Windows (C++), unified through a JavaScript bridge layer. The server-side is hosted at swyng.site.
 
 ## Development Commands
 

package/README.md

@@ -1,8 +1,8 @@
-#### [Sign up with SwyngPush](https://swyngpush.site) to use CodePush
+#### [Sign up with SwyngPush](https://swyng.site) to use CodePush
 
 # React Native Module for SwyngPush
 
-This plugin provides client-side integration for the [SwyngPush service](https://swyngpush.site), allowing you to easily add over-the-air updates to your React Native app(s).
+This plugin provides client-side integration for the [SwyngPush service](https://swyng.site), allowing you to easily add over-the-air updates to your React Native app(s).
 
 - [How does it work?](#how-does-it-work)
 - [Supported React Native Platforms](#supported-react-native-platforms)
@@ -71,7 +71,7 @@ _Note: CodePush only works with Video components when using `require` in the sou
 
 ## Getting Started
 
-Once you've followed the general-purpose ["getting started"](https://console.swyngpush.site/docs) instructions for setting up your SwyngPush account, you can start CodePush-ifying your React Native app by running the following command from within your app's root directory:
+Once you've followed the general-purpose ["getting started"](https://console.swyng.site/docs) instructions for setting up your SwyngPush account, you can start CodePush-ifying your React Native app by running the following command from within your app's root directory:
 
 ```shell
 yarn add @swyng/react-native-code-push
@@ -244,7 +244,7 @@ This is not necessarily the case for `updateDialog`, since it won't force the us
 
 Once your app is configured and distributed to your users, and you have made some JS or asset changes, it's time to release them. The recommended way to release them is using the `create_bundle` command in the SwyngPush CLI, which will bundle your JavaScript files, asset files, and release the update to the SwyngPush server.
 
-*NOTE: Before you can start releasing updates, please log into [SwyngPush](https://swyngpush.site) by running the `npx @swyng/cli login -u <username> -p <password>` command.*
+*NOTE: Before you can start releasing updates, please log into [SwyngPush](https://swyng.site) by running the `npx @swyng/cli login -u <username> -p <password>` command.*
 
 In its most basic form, this command only requires some parameters:
 
@@ -258,7 +258,7 @@ The `create_bundle` command enables such a simple workflow because it provides m
 
 The CodePush client supports differential updates, so even though you are releasing your JS bundle and assets on every update, your end users will only actually download the files they need. The service handles this automatically so that you can focus on creating awesome apps and we can worry about optimizing end user downloads.
 
-For more details about how the `create_bundle` command works, as well as the various parameters it exposes, refer to the [CLI docs](https://console.swyngpush.site/docs).
+For more details about how the `create_bundle` command works, as well as the various parameters it exposes, refer to the [CLI docs](https://console.swyng.site/docs).
 
 ### Dynamic Deployment Assignment
 

package/SECURITY.md

@@ -6,7 +6,7 @@ If you believe you have found a security vulnerability in this repository, pleas
 
 **Please do NOT report security vulnerabilities through public GitHub issues.**
 
-Instead, please send an email to [security@swyngpush.site](mailto:security@swyngpush.site).
+Instead, please send an email to [security@swyng.site](mailto:security@swyng.site).
 
 You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
 

package/docs/api-js.md

@@ -10,7 +10,7 @@ The following sections describe the shape and behavior of these APIs in detail:
 
 ### JavaScript API Reference
 
-When you require `react-native-code-push`, the module object provides the following top-level methods in addition to the root-level [component decorator](#codepush):
+When you require `@swyng/react-native-code-push`, the module object provides the following top-level methods in addition to the root-level [component decorator](#codepush):
 
 * [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 necessary if your app explicitly disallowed restarts via the `disallowRestart` method.
 
@@ -128,7 +128,7 @@ The `codePush` decorator accepts an "options" object that allows you to customiz
 
 * __minimumBackgroundDuration__ *(Number)* - Specifies the minimum number of seconds that the app needs to have been in the background before restarting the app. This property only applies to updates which are installed using `InstallMode.ON_NEXT_RESUME` or `InstallMode.ON_NEXT_SUSPEND`, and can be useful for getting your update in front of end users sooner, without being too obtrusive. Defaults to `0`, which has the effect of applying the update immediately after a resume or unless the app suspension is long enough to not matter, regardless how long it was in the background.
 
-* __updateDialog__ *(UpdateDialogOptions)* - An "options" object used to determine whether a confirmation dialog should be displayed to the end user when an update is available, and if so, what strings to use. Defaults to `null`, which has the effect of disabling the dialog completely. Setting this to any truthy value will enable the dialog with the default strings, and passing an object to this parameter allows enabling the dialog as well as overriding one or more of the default strings. Before enabling this option within an App Store-distributed app, please refer to [this note](https://github.com/swyngpush/react-native#app-store).
+* __updateDialog__ *(UpdateDialogOptions)* - An "options" object used to determine whether a confirmation dialog should be displayed to the end user when an update is available, and if so, what strings to use. Defaults to `null`, which has the effect of disabling the dialog completely. Setting this to any truthy value will enable the dialog with the default strings, and passing an object to this parameter allows enabling the dialog as well as overriding one or more of the default strings. Before enabling this option within an App Store-distributed app, please refer to [this note](https://github.com/swyng-it/swyng#app-store).
 
     The following list represents the available options and their defaults:
 

package/docs/multi-deployment-testing-android.md

@@ -2,7 +2,7 @@
 
 > NOTE
 >
-> Complete demo configured with "multi-deployment testing" feature is [here](https://github.com/swyngpush/react-native/files/1314118/rncp1004.zip).
+> Complete demo configured with "multi-deployment testing" feature is [here](https://github.com/swyng-it/swyng/files/1314118/rncp1004.zip).
 
 The [Android Gradle plugin](https://google.github.io/android-gradle-dsl/current/index.html) allows you to define custom config settings for each "build type" (like debug, release). This mechanism allows you to easily configure your debug builds to use your CodePush staging deployment key and your release builds to use your CodePush production deployment key.
 

package/docs/multi-deployment-testing-ios.md

@@ -3,8 +3,8 @@
 > NOTE
 >
 > Complete demos configured with "multi-deployment testing" feature are [here]:
-> *  **without using cocoa pods**: [link](https://github.com/swyngpush/react-native/files/1259957/rncp976.copy.zip)
-> *  **using cocoa pods**: [link](https://github.com/swyngpush/react-native/files/1172217/rncp893.copy.zip)
+> *  **without using cocoa pods**: [link](https://github.com/swyng-it/swyng/files/1259957/rncp976.copy.zip)
+> *  **using cocoa pods**: [link](https://github.com/swyng-it/swyng/files/1172217/rncp893.copy.zip)
 
 Xcode allows you to define custom build settings for each "configuration" (like debug, release), which can then be referenced as the value of keys within the `Info.plist` file (like the `CodePushDeploymentKey` setting). This mechanism allows you to easily configure your builds to produce binaries, which are configured to synchronize with different CodePush deployments.
 
@@ -54,6 +54,6 @@ And that's it! Now when you run or build your app, your staging builds will auto
 
 *NOTE: CocoaPods users may need to run `pod install` before building with their new release configuration.*
 
-*Note: If you encounter the error message `ld: library not found for ...`, please consult [this issue](https://github.com/swyngpush/react-native/issues/426) for a possible solution.*
+*Note: If you encounter the error message `ld: library not found for ...`, please consult [this issue](https://github.com/swyng-it/swyng/issues/426) for a possible solution.*
 
 Additionally, if you want to give them seperate names and/or icons, you can modify the `Product Bundle Identifier`, `Product Name` and `Asset Catalog App Icon Set Name` build settings, which will allow your staging builds to be distinguishable from release builds when installed on the same device.

package/docs/setup-android.md

@@ -96,7 +96,7 @@ In order to effectively make use of the `Staging` and `Production` deployments t
 
 ### Code Signing setup
 
-Starting with CLI version **2.1.0** you can self sign bundles during release and verify its signature before installation of update. For more info about Code Signing please refer to [relevant code-push documentation section](https://github.com/swyngpush/code-push/tree/v3.0.1/cli#code-signing). In order to use Public Key for Code Signing you need to do following steps:
+Starting with CLI version **2.1.0** you can self sign bundles during release and verify its signature before installation of update. For more info about Code Signing please refer to [relevant code-push documentation section](https://github.com/swyng-it/swyng/tree/v3.0.1/cli#code-signing). In order to use Public Key for Code Signing you need to do following steps:
 
    Add `CodePushPublicKey` string item to `/path_to_your_app/android/app/src/main/res/values/strings.xml`. It may looks like this:
 
@@ -116,6 +116,6 @@ zwIDAQAB
  ```
 
 ### Expo Integration 
-1. A pure expo react-native is not supported yet. We are planning to look into this after a while. See https://github.com/CodePushNext/react-native-code-push/issues/5
+1. A pure expo react-native is not supported yet. We are planning to look into this after a while. See https://github.com/swyng-it/swyng/issues/5
 2. A bare react-native app with expo sdk is supported, but you have to initialize rn app without `ReactNativeHostWrapper` of expo. It seems `ReactNativeHostWrapper` overrides `getJsBundleFile` internally, which prevents `CodePush` from being configured correctly.     
    https://github.com/expo/expo/issues/25865

package/docs/setup-ios.md

@@ -91,7 +91,7 @@ Once you've acquired the CodePush plugin, you need to integrate it into the Xcod
 
 CodePush plugin makes HTTPS requests to the following domains:
 
-- api.swyngpush.site
+- api.swyng.site
 
 If you want to change the default HTTP security configuration for any of these domains, you have to define the [`NSAppTransportSecurity` (ATS)][ats] configuration inside your __Info.plist__ file:
 
@@ -104,7 +104,7 @@ If you want to change the default HTTP security configuration for any of these d
     <dict>
       <key>NSExceptionDomains</key>
       <dict>
-        <key>api.swyngpush.site</key>
+        <key>api.swyng.site</key>
         <dict><!-- read the ATS Apple Docs for available options --></dict>
       </dict>
     </dict>
@@ -120,7 +120,7 @@ Before doing anything, please [read the docs][ats] first.
 
 ### Code Signing setup
 
-Starting with CLI version **2.1.0** you can self sign bundles during release and verify its signature before installation of update. For more info about Code Signing please refer to [relevant code-push documentation section](https://github.com/swyngpush/code-push/tree/v3.0.1/cli#code-signing).
+Starting with CLI version **2.1.0** you can self sign bundles during release and verify its signature before installation of update. For more info about Code Signing please refer to [relevant code-push documentation section](https://github.com/swyng-it/swyng/tree/v3.0.1/cli#code-signing).
 
 In order to configure Public Key for bundle verification you need to add record in `Info.plist` with name `CodePushPublicKey` and string value of public key content. Example:
 

package/expo.js

@@ -242,7 +242,7 @@ const withAndroidGradle = (config) => {
       let content = modConfig.modResults.contents;
       
       // This part adds the codepush.gradle apply line and is correct.
-      const codePushApplyLine = 'apply from: "../../node_modules/@code-push-next/react-native-code-push/android/codepush.gradle"';
+      const codePushApplyLine = 'apply from: "../../node_modules/@swyng/react-native-code-push/android/codepush.gradle"';
       if (!content.includes(codePushApplyLine)) {
         content += `\n${codePushApplyLine}\n`;
       }

package/package.json

@@ -1,17 +1,17 @@
 {
   "name": "@swyng/react-native-code-push",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "React Native plugin for SwyngPush over-the-air updates",
   "main": "CodePush.js",
   "typings": "typings/react-native-code-push.d.ts",
-  "homepage": "https://swyngpush.site",
+  "homepage": "https://swyng.site",
   "keywords": [
     "react-native",
     "code-push",
     "ota-updates",
     "swyngpush"
   ],
-  "author": "Swyng <support@swyngpush.site>",
+  "author": "Swyng <support@swyng.site>",
   "license": "MIT",
   "publishConfig": {
     "access": "public"
@@ -42,7 +42,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "https://github.com/swyngpush/react-native"
+    "url": "https://github.com/swyng-it/swyng"
   },
   "dependencies": {
     "code-push": "4.2.3",
@@ -88,4 +88,4 @@
       "postunlink": "node node_modules/@swyng/react-native-code-push/scripts/postunlink/run"
     }
   }
-}
+}

package/request-fetch-adapter.js

@@ -37,7 +37,7 @@ module.exports = {
 
 function getHttpMethodName(verb) {
   // Note: This should stay in sync with the enum definition in
-  // https://github.com/swyngpush/code-push/blob/master/sdk/script/acquisition-sdk.ts#L6
+  // https://github.com/swyng-it/swyng/blob/master/sdk/script/acquisition-sdk.ts#L6
   return [
     "GET",
     "HEAD",

package/scripts/generateBundledResourcesHash.js

@@ -83,7 +83,7 @@ function addJsBundleAndMetaToManifest() {
             // "CodePushHash.json" file name breaks flow type checking.
             // To fix the issue we need to delete "CodePushHash.json" file and
             // use "CodePushHash" file name instead to store the hash value.
-            // Relates to https://github.com/swyngpush/react-native/issues/577
+            // Relates to https://github.com/swyng-it/swyng/issues/577
             var oldSavedResourcesManifestPath = assetsDir + "/" + CODE_PUSH_HASH_OLD_FILE_NAME;
             if (fs.existsSync(oldSavedResourcesManifestPath)) {
                 fs.unlinkSync(oldSavedResourcesManifestPath);

package/scripts/postlink/android/postlink.js

@@ -37,14 +37,14 @@ module.exports = () => {
         } else {
             return Promise.reject(`Couldn't find Android application entry point. You might need to update it manually. \
     Please refer to plugin configuration section for Android at \
-    https://github.com/swyngpush/react-native/blob/master/docs/setup-android.md#plugin-configuration-for-react-native-lower-than-060-android for more details`);
+    https://github.com/swyng-it/swyng/blob/master/docs/setup-android.md#plugin-configuration-for-react-native-lower-than-060-android for more details`);
         }
     }
 
     if (!fs.existsSync(buildGradlePath)) {
         return Promise.reject(`Couldn't find build.gradle file. You might need to update it manually. \
     Please refer to plugin installation section for Android at \
-    https://github.com/swyngpush/react-native/blob/master/docs/setup-android.md#plugin-installation-android---manual`);
+    https://github.com/swyng-it/swyng/blob/master/docs/setup-android.md#plugin-installation-android---manual`);
     }
 
     // 2. Add the codepush.gradle build task definitions

package/scripts/postlink/ios/postlink.js

@@ -16,7 +16,7 @@ module.exports = () => {
     if (!appDelegatePath) {
         return Promise.reject(`Couldn't find AppDelegate. You might need to update it manually \
     Please refer to plugin configuration section for iOS at \
-    https://github.com/swyngpush/react-native#plugin-configuration-ios`);
+    https://github.com/swyng-it/swyng#plugin-configuration-ios`);
     }
 
     var appDelegateContents = fs.readFileSync(appDelegatePath, "utf8");
@@ -84,7 +84,7 @@ module.exports = () => {
     if (!plistPath) {
         return Promise.reject(`Couldn't find .plist file. You might need to update it manually \
     Please refer to plugin configuration section for iOS at \
-    https://github.com/swyngpush/react-native#plugin-configuration-ios`);
+    https://github.com/swyng-it/swyng#plugin-configuration-ios`);
     }
 
     var plistContents = fs.readFileSync(plistPath, "utf8");

package/scripts/postunlink/android/postunlink.js

@@ -31,7 +31,7 @@ module.exports = () => {
         } else {
             console.log(`Couldn't find Android application entry point. You might need to update it manually. \
     Please refer to plugin configuration section for Android at \
-    https://github.com/swyngpush/react-native/blob/master/docs/setup-android.md#plugin-configuration-for-react-native-lower-than-060-android for more details`);
+    https://github.com/swyng-it/swyng/blob/master/docs/setup-android.md#plugin-configuration-for-react-native-lower-than-060-android for more details`);
         }
     }
 
@@ -41,7 +41,7 @@ module.exports = () => {
     if (!fs.existsSync(buildGradlePath)) {
         console.log(`Couldn't find build.gradle file. You might need to update it manually. \
     Please refer to plugin installation section for Android at \
-    https://github.com/swyngpush/react-native/blob/master/docs/setup-android.md#plugin-installation-android---manual`);
+    https://github.com/swyng-it/swyng/blob/master/docs/setup-android.md#plugin-installation-android---manual`);
     } else {
         var buildGradleContents = fs.readFileSync(buildGradlePath, "utf8");
         var codePushGradleLink = linkTools.codePushGradleLink;

package/scripts/postunlink/ios/postunlink.js

@@ -14,7 +14,7 @@ module.exports = () => {
     if (!appDelegatePath) {
         console.log(`Couldn't find AppDelegate. You might need to update it manually \
     Please refer to plugin configuration section for iOS at \
-    https://github.com/swyngpush/react-native#plugin-configuration-ios`);
+    https://github.com/swyng-it/swyng#plugin-configuration-ios`);
     } else {
         var appDelegateContents = fs.readFileSync(appDelegatePath, "utf8");
 
@@ -68,7 +68,7 @@ module.exports = () => {
     if (!plistPath) {
         return Promise.reject(`Couldn't find .plist file. You might need to update it manually \
     Please refer to plugin configuration section for iOS at \
-    https://github.com/swyngpush/react-native#plugin-configuration-ios`);
+    https://github.com/swyng-it/swyng#plugin-configuration-ios`);
     }
 
     var plistContents = fs.readFileSync(plistPath, "utf8");

package/scripts/tools/linkToolsIos.js

@@ -22,7 +22,7 @@ exports.getJsCodeLocationPatch = function(defaultJsCodeLocationAssignmentStateme
   #endif`;
 }
 
-// Fix for https://github.com/swyngpush/react-native/issues/477
+// Fix for https://github.com/swyng-it/swyng/issues/477
 // Typical location of AppDelegate.m for newer RN versions: $PROJECT_ROOT/ios/<project_name>/AppDelegate.m
 // Let's try to find that path by filtering the whole array for any path containing <project_name>
 // If we can't find it there, play dumb and pray it is the first path we find.
@@ -71,7 +71,7 @@ exports.getPlistPath = function() {
     }
 
     //also remove surrounding quotes from plistPathValue to get correct path resolved
-    //(see https://github.com/swyngpush/react-native/issues/534#issuecomment-302069326 for details)
+    //(see https://github.com/swyng-it/swyng/issues/534#issuecomment-302069326 for details)
     return path.resolve(path.dirname(xcodeProjectPath), '..', plistPathValue.replace(/^"(.*)"$/, '$1'));
 }