FST_ERR_VALIDATION - When checking for a CodePush update, I get a 400 Bad Request error with validation failure on deployment_key.

[NikhilMasurkar]

Starting CodePush update check...
NewHome.js:398 Error checking for update: Error: 400: {"statusCode":400,"code":"FST_ERR_VALIDATION","error":"Bad Request","message":"querystring/deployment_key Must be from 10 to 100 characters, querystring/deployment_key Must contain only letters, numbers, underscores, or hyphens"}
at call (native)
at CodePushError (http://localhost:8081/index.bundle//&platform=ios&dev=true&lazy=true&minify=false&inlineSourceMap=false&modulesOnly=false&runModule=true&excludeSource=true&sourcePaths=url-server&app=com.indigolearn.onefin.dev:139176:30)
at call (native)
at CodePushHttpError (http://localhost:8081/index.bundle//&platform=ios&dev=true&lazy=true&minify=false&inlineSourceMap=false&modulesOnly=false&runModule=true&excludeSource=true&sourcePaths=url-server&app=com.indigolearn.onefin.dev:139186:30)
at anonymous (http://localhost:8081/index.bundle//&platform=ios&dev=true&lazy=true&minify=false&inlineSourceMap=false&modulesOnly=false&runModule=true&excludeSource=true&sourcePaths=url-server&app=com.indigolearn.onefin.dev:139002:95)
at ?anon_0_ (http://localhost:8081/index.bundle//&platform=ios&dev=true&lazy=true&minify=false&inlineSourceMap=false&modulesOnly=false&runModule=true&excludeSource=true&sourcePaths=url-server&app=com.indigolearn.onefin.dev:138718:19)
at next (native)
at asyncGeneratorStep (http://localhost:8081/index.bundle//&platform=ios&dev=true&lazy=true&minify=false&inlineSourceMap=false&modulesOnly=false&runModule=true&excludeSource=true&sourcePaths=url-server&app=com.indigolearn.onefin.dev:22342:19)
at _next (http://localhost:8081/index.bundle//&platform=ios&dev=true&lazy=true&minify=false&inlineSourceMap=false&modulesOnly=false&runModule=true&excludeSource=true&sourcePaths=url-server&app=com.indigolearn.onefin.dev:22356:29)
at tryCallOne (address at InternalBytecode.js:1:1180)
at anonymous (address at InternalBytecode.js:1:1874)

I added the following keys in Info.plist for both prod and test:

CodePushDeploymentKey
$(CODEPUSH_KEY)
CodePushServerURL
https://api.revopush.org

sdk version

"@revopush/react-native-code-push": "^1.4.0",
react native version 0.79.2

[revopushbot]

thanks for report. We've investigated your request and see on the servers side the following URI is involved

/v0.1/public/codepush/update_check?deployment_key=&app_version=3.4.1&client_unique_id=799CB9EB-166C-4F50-B752-207A4CD8AD6C

it means deployment_key did not get value so since it's mandatory parameter to identify your deployment the request is rejected.

We will double check scenario on our side too but meanwhile we ask you to double check steps described here https://docs.revopush.org/sdk/multi-deployment-testing-ios . So far we are no sure if issue is in SDK itself and not in iOS build process and Xcode setup where potentially due to some reasons User Defined values are not resolved during the build.

[NikhilMasurkar]

Thanks for your response. I’ve double-checked all the steps mentioned in your documentation carefully.

About a week ago, I implemented the same setup, and it was working fine. However, after switching to another account and checking the production-level keys, the issue started appearing.

Please check this from your end and let me know if you need any additional information — I’ll be happy to share it.

[NikhilMasurkar]

@revopushbot can you please check what the issue

this is my lastest keys

got same erorr

const checkForCodePushUpdates = async () => {
// if (!isProdMode() || !shouldCheckCodePush()) return;
let update = null;
try {
update = await codePush.checkForUpdate();
} catch (error) {
console.log(error);
}
// If mandatory update -> Init CodePush sync flow
if (update && update.isMandatory) {
const {IMMEDIATE} = codePush.InstallMode;
await codePush.sync(
{installMode: IMMEDIATE},
(status) => {
const {
UP_TO_DATE,
UPDATE_IGNORED,
UNKNOWN_ERROR,
SYNC_IN_PROGRESS,
CHECKING_FOR_UPDATE,
} = codePush.SyncStatus;
if ([SYNC_IN_PROGRESS, CHECKING_FOR_UPDATE].includes(status)) {
} else if (
[UP_TO_DATE, UPDATE_IGNORED, UNKNOWN_ERROR].includes(status)
) {
} else {
setShowCodePushWidget(true);
}
},
(DownloadProgress) => {
setCodePushDownloadProgress(DownloadProgress);
},
);
} else if (update) {
const {ON_NEXT_RESTART} = codePush.InstallMode;
await codePush.sync({installMode: ON_NEXT_RESTART});
}
};

CodePushDeploymentKey
$(CODEPUSH_KEY)
CodePushServerURL
https://api.revopush.org

[revopushbot]

we checked your key and it is totally fine. If you send it properly we return data back. Try with curl

curl --location 'https://api.revopush.org/v0.1/public/codepush/update_check?deployment_key=BCowy0AlUyjSekkaMPmPXMjewmPAV1b5utrvzg&app_version=3.4.1&package_hash=b767abc17f70273bf525631d06066820535080928fb1e743c9718e36f29942a3&client_unique_id=2E50D870-4C7F-4A14-BE1C-2A44341145FC' 

it gives you

{
    "update_info": {
        "is_available": true,
        "update_app_version": false,
        "should_run_binary_version": false,
        "download_url": "https://blob.revopush.org/3QVjcv_DZWt5yoduirtdlW9envzuV1b5utrvzg",
        "package_size": 1780243,
        "description": "",
        "is_mandatory": true,
        "label": "v3",
        "package_hash": "c2d9c232471f5176775eeef44cf86d0fcd6eeaebbea18d82388c4c93d29c6df2",
        "app_version": "3.4.1",
        "target_binary_range": "3.4.1"
    }
}

having said that the issue may be related to how you build the app. Despite the fact you shared your Xcode screenshoot where values are resolved on actual runtime $(CODEPUSH_KEY) resolves to nothing. We suggest you to double check final IPA file you build and verify whether it has correct value in .plist`.

[NikhilMasurkar]

After checking directly in the production environment, it’s working fine.
However, in staging, it’s not working — even though I followed the exact same setup and method for both environments.
It seems there might be an issue specific to the staging configuration.

Could you please check and let me know how I can resolve this?

[revopushbot]

happy to hear that it works well on prod environment. From put side there is no difference between keys and used approaches between Staging env and Production. However, potentially you may create slightly different builds of the application for staging. For example, here we describe how to embed codepush into native part of the app (example for iOS)

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
  #if DEBUG
    return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index"];
  #else
    return [CodePush bundleURL];
  #endif
}

so potentially for Staging version of the app you have DEBUG enable and as result no return [CodePush bundleURL]; is returned. Please check the difference between builds for Staging and Production to ensure you call code push APIs with a correct key.

[revopushbot]

@NikhilMasurkar is issue persist on your side or we may close it?