APK Signature

0 favourites
  • 5 posts
  • I'm trying to send a signed APK to Google Play Console, but they don't accept the APK, it says there is an error with the signature, but it's the same signature I always sent. Has this happened to anyone else?

    I used R255 and R257 to export my game.

    Error: You have uploaded an APK with an invalid signature. Apksigner error: ERROR (APK Signature Scheme v2 signer #0): APK integrity check failed. CHUNKED_SHA256 digest mismatch. Expected: <9251813ff2d75bf750f4a438e5b74cee2dea5242768566f26c3cd82b977f34c7>, current: <54d9f17ae171412705ef2a5ad4472a25da245b7cccd3c5baff2f7b0dd1d850dd>

  • Are you exporting in Android Studio or using our Build server ?

    Are you sure you are using the correct keystore to sign your APK ? The message could suggest otherwise.

  • I'm trying to send a signed APK to Google Play Console, but they don't accept the APK, it says there is an error with the signature, but it's the same signature I always sent. Has this happened to anyone else?

    I used R255 and R257 to export my game.

    Error: You have uploaded an APK with an invalid signature. Apksigner error: ERROR (APK Signature Scheme v2 signer #0): APK integrity check failed. CHUNKED_SHA256 digest mismatch. Expected: <9251813ff2d75bf750f4a438e5b74cee2dea5242768566f26c3cd82b977f34c7>, current: <54d9f17ae171412705ef2a5ad4472a25da245b7cccd3c5baff2f7b0dd1d850dd>

    Hi, it happened to me with the R255, Google Play support advised me to send a new signature, after sending I waited 2 days for approval. Now I use the R256 and I have no problems.

  • > I'm trying to send a signed APK to Google Play Console, but they don't accept the APK, it says there is an error with the signature, but it's the same signature I always sent. Has this happened to anyone else?

    >

    > I used R255 and R257 to export my game.

    >

    > Error: You have uploaded an APK with an invalid signature. Apksigner error: ERROR (APK Signature Scheme v2 signer #0): APK integrity check failed. CHUNKED_SHA256 digest mismatch. Expected: <9251813ff2d75bf750f4a438e5b74cee2dea5242768566f26c3cd82b977f34c7>, current: <54d9f17ae171412705ef2a5ad4472a25da245b7cccd3c5baff2f7b0dd1d850dd>

    Hi, it happened to me with the R255, Google Play support advised me to send a new signature, after sending I waited 2 days for approval. Now I use the R256 and I have no problems.

    Google Support guided me to do a procedure to check if my signature was the same as the signature registered on the server, I checked and the signature was correct. I suspected the problem was with the package, so I did a lot of builds until one worked and Google accepted my update. I concluded that the problem is the compilation process on the server. This is annoying because I have to compile many times before one works.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • If you run in to a bug or issue in Construct 3, please post it to the GitHub issue tracker here:

    github.com/Scirra/Construct-3-bugs

    You must follow the bug report guidelines or your issue will be closed without investigation

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)