Closed danielpetersson closed 2 weeks ago
Yes, it is working. It was accidentally posted here but should have been posted to https://github.com/microsoft/code-push-server.
Den ons 16 okt. 2024 13:25MikhailSuendukov @.***> skrev:
Hello! Thank you for reaching out. Could you let us know if you've found a solution to your issue? If so, we’d appreciate it if you could share the details with us.
— Reply to this email directly, view it on GitHub https://github.com/microsoft/react-native-code-push/issues/2766#issuecomment-2416522972, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABF2LHYMTS3RDQNZ4OOIHHLZ3ZEJ7AVCNFSM6AAAAABQA5BJDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJWGUZDEOJXGI . You are receiving this because you modified the open/close state.Message ID: @.***>
We are currently using appcenter codepush CLI to release update. We are using --private-key-path to sign the update. Releasing with the react-native-code-push CLI doesn't have support for --private-key-path which causes the app (which verifies the downloaded update) to output:
Should we sign the update as a pre-step to "code-push-standalone release-react" or can we, and is it recommended, to somehow disable the need of validating signing in our app?