You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found out that AppCenter CLI 2.13.0 and later cannot release updates signed with private key of length lower than 2048 bit. I encountered this problem after upgrading CLI to the latest version with my 512-bit key I created few years ago when 512 was the default value. This was due to a breaking change in jsonwebtoken v9 that rejects RSA keys shorter than 2048 bit.
Even though the default key size is now 2048 when being generated, it might save someone's time in the future to mention the minimum key size in the documentation. (Since the CLI simply returned exit code 3 and debug mode vaguely said "The specified signing key file was not valid", so considerable amount of time spent in investigation)
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: a2c2bd47-97e3-abc8-fbdd-305f0c631827
Version Independent ID: 318718e7-a38a-7cc5-01a4-7ce0153c4398
I found out that AppCenter CLI 2.13.0 and later cannot release updates signed with private key of length lower than 2048 bit. I encountered this problem after upgrading CLI to the latest version with my 512-bit key I created few years ago when 512 was the default value. This was due to a breaking change in
jsonwebtoken
v9 that rejects RSA keys shorter than 2048 bit.Even though the default key size is now 2048 when being generated, it might save someone's time in the future to mention the minimum key size in the documentation. (Since the CLI simply returned
exit code 3
and debug mode vaguely said "The specified signing key file was not valid", so considerable amount of time spent in investigation)Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: