Android updates seem to be blocked when I use a public.pem

[CoryWritesCode]

I have the private.pem file in the command when I upload a CodePush version but the download always comes back with this on Android.

command I use to upload

revopush release-react \
            qwick_android \
            android \
            --deploymentName development \
            --useHermes \
            --outputDir ./build \
            --sourcemapOutput ./sourcemap \
            --privateKeyPath private.pem

[kit2o]

@CoryWritesCode hey thank you for the report.

For Android it is important to use --outputDir with root CodePush dir to support JWT signing

like:

revopush release-react \
            qwick_android \
            android \
            --deploymentName development \
            --useHermes \
            --outputDir ./build/CodePush \
            --sourcemapOutput ./sourcemap \
            --privateKeyPath private.pem

We also updated documentation for sentry https://docs.revopush.org/cicd/sentry

[CoryWritesCode]

Thanks @kit2o I'll give it a look!

[CoryWritesCode]

@kit2o sorry I was looking in the wrong place.
I'm still getting [CodePush] The update could not be verified because it was not signed by a trusted party.

[revopushbot]

@CoryWritesCode the only place where this exception is raised is this. It means now you do have both public key in your app as well as hash value that came with a bundle. However, the method can return null either when hashes do not match or any issue with JWT parsing. In case case of issues with JWT parsing it would print an exception.

would you please:

• double check if you have any exceptions printed. If yes please share it.
• double check if your public/private keys match each other. Keep in mind that in case of Android in strings.xml key should look like this (new lines do matter for RSA public keys)

    <string name="CodePushPublicKey">-----BEGIN PUBLIC KEY-----
        MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5hEmN/yPJDByIaHCKmXF
        2BL559+4hW1Oq4MBDmYx422pZgWZ1p8AnK0FsU83g/93306K1V+6xGOhUkUrI2SW
        HmNJjJSNKhq+XLTvnNBDCYtbSKLB7BrCKE56hxEbcOjJLfMyBb67d7De/Iim6zk8
        DgozWLjSPaaSxAWKzQa+hIoK7189PBuL/c1zL9yJZEAizp1B+tEmsQnKB6nAUWio
        zFYMG4EG6JyakFbNd36mRAxKIjFw6QbNs4nlxbYok3xbN+VxlW1VgDHCz7oZlV+b
        XqmOVlk/emmiosl1btJLdIOCsGgxEiog8ZoSFmqmb17bQ/5ZAGjzq4VtglaG4vGy
        CwIDAQAB
        -----END PUBLIC KEY-----</string>

Here is exact commands we use to generate these private/public pair https://docs.revopush.org/cli/code-signing#code-signing-for-codepush so please double check if you use (we tested using openssl LibreSSL 3.3.6 but should not be matter).

[CoryWritesCode]

I'll check on this today and hopefully get back to you soon. Thanks for your help @kit2o

[revopushbot]

any updates from your side @CoryWritesCode?

[CoryWritesCode]

I have a ticket to work on this this sprint so I should be able to get back to you here soon. Thanks

[CoryWritesCode]

Had a crisis at work and it got pushed off. Will work on it this week hopefully.

[revopushbot]

@CoryWritesCode please let us know it issue persist on one of the latest releases. We haven't heard similar issues from other clients wonder this is something with your key and/or app-specific config.