Context

When pushing an OTA update via code-push release-react, some users may find that native social login methods — such as Apple Sign In, Google Sign-In, and Facebook Login — stop working after installing the update, while the rest of the app continues to function normally. This article explains why this can happen and how to recover from it.

Answer

CodePush OTA updates only replace the JavaScript bundle and assets — they cannot modify native iOS/Android binaries or native SDKs. Native integrations like Apple Sign In, Google Sign-In, and Facebook Login rely on implementations already compiled into the installed binary.

If social logins break after an OTA update but work fine with the store binary, the most likely cause is a mismatch between the JS side of an authentication SDK (or the native configuration it expects) in the OTA bundle and what the shipped binary was compiled against. This causes the native bridge calls to fail while pure-JS features continue to work normally.

To investigate, check the following:

1. Review any changes in the OTA bundle related to authentication libraries or their configuration (e.g., updated SDK versions, changed initialization parameters, or modified auth flow logic).

2. Ensure the JS-side auth SDK version in the OTA bundle is compatible with the native SDK version compiled into the store binary.

3. Verify that no native configuration files (e.g., GoogleService-Info.plist, google-services.json, or Facebook app settings) were expected to change as part of the update — these cannot be delivered via OTA.

Recovery options if a bad OTA update has already been deployed:

• Disable the release to prevent additional devices from downloading it:
  code-push patch <app> Production --disabled true
  Note: this does not revert devices that have already installed the update.

• Roll back using code-push rollback if a prior OTA release exists on the deployment. If this was the first OTA release, rollback will not be available.

• Push a new fixed mandatory OTA update — this is the recommended recovery path when rollback is not possible. Devices that installed the bad bundle will receive the new fixed bundle automatically.

There are no known issues with CodePush itself that would universally cause native social logins to break. If the issue persists after ruling out JS/native configuration mismatches, consider reaching out to Codemagic support with details about the specific SDK versions and any recent dependency changes.