Same keystores but different SHA1 fingerprints

To follow up -

I just noticed that Expo generated a new keystore today for an existing app even though there was no instructions to do so.

The only changes I did was adding a scheme field to the app.json file.

Could anyone come in to help for this?