Fixing broken links (#3461)

* CodePush updates control

Explains how to have control over launching updates

* Update telegram.md (#3433)

* Update telegram.md

* Update content/yaml-notification/telegram.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Codepush analytics (#3460)

* codepush analytics with other options

* codepush analytics

* api removal

* few more clarifying points

* fixing links

* broken links and section update

---------

Co-authored-by: Tirth Patel <tirth@nevercode.io>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: 3 people

content/rn-codepush/debugging-and-common-issues.md

@@ -123,6 +123,26 @@ Most monitoring platforms provide documentation for integrating CodePush release
 
 The following issues are common when releasing CodePush updates.
 
+### Native binary without the CodePush SDK
+
+OTA updates only install on native builds that already contain the CodePush SDK. If the SDK was recently added to the project but the store binary users have installed predates that change, `release-react` will publish successfully and the update will appear in the deployment history, but **no client will pick it up** — there is nothing on the device to check the server.
+
+Symptoms:
+
+- Release shows in `code-push deployment history <APP> <DEPLOYMENT>` with active installs staying at zero.
+- No `[CodePush]` log entries appear on device when you open the app, even with good network connectivity.
+- The issue affects all users, not a subset.
+
+Fix:
+
+1. Confirm the SDK is wired up in the React Native project (see [Setup](/rn-codepush/setup/#add-codepush-to-a-react-native-app)).
+2. Rebuild the app so the native binary includes the SDK, and install that build on the devices that should receive updates:
+   - **Staging:** a fresh dev or internal-distribution build on your test devices is enough; no store release needed.
+   - **Production:** publish to the App Store / Google Play and wait for users to update.
+3. Subsequent `release-react` calls against the matching deployment will then reach those devices over the air.
+
+This is a one-time gate per deployment when first adopting CodePush; after devices are on an SDK-enabled binary, the regular OTA flow applies. See [Concepts](/rn-codepush/concepts/#prerequisite-a-native-build-with-the-sdk) for the underlying reason.
+
 ### Wrong binary version targeting
 
 Updates are only installed if the device's app version satisfies the `targetBinaryVersion` constraint.

content/yaml-quick-start/building-a-react-native-app.md

@@ -276,7 +276,7 @@ If you are going to publish your app to App Store Connect or Google Play, each u
 
 ## OTA Updates with CodePush
 
-Our hosted CodePush service lets you publish OTA updates for React Native projects directly to users' devices, without going through the App Store or Google Play. Read the [concepts page](../rn-codepush/codepush-concepts/) for how it works, or the [setup page](../rn-codepush/setup-codepush/) to get started.
+Our hosted CodePush service lets you publish OTA updates for React Native projects directly to users' devices, without going through the App Store or Google Play. Read the [concepts page](../rn-codepush/concepts/) for how it works, or the [setup page](../rn-codepush/setup/) to get started.
 
 
 ## Conclusion