Switch TWA from pointing to testing.openlibrary.org to openlibrary.org

[cdrini]

Note this is causing edits from the app to behave strangely / not show up (as is the case on testing.openlibrary.org)

Stakeholders

@bicolino34

[bicolino34]

TWA now points to openlibrary.org

[SaravgiYash]

@cdrini @bicolino34 It would be great if we can generate a new APK and update it on Google Play Store because currently, it's using the testing.openlibrary.org APK

I think we need to create a new APK with openlibrary URL and also change the SHA to the one provided by Play Store.

From Stackoverflow: https://stackoverflow.com/questions/54597728/trusted-web-activity-address-bar-not-hide-chrome-for-android-72

You may have opted into having Google Play sign your releases with a key they generated and only use your key for the upload. If you did, go to Google Play Console Release Management -> App Signing and copy the App signing certificate SHA-256 fingerprint and put it into the assetlinks.json file.

[bicolino34]

Indeed. It is still pointing to testing.openlibrary.org. my mistake. Sorry for that

[SaravgiYash]

Generating a new APK and updating the SHA-256 (from Play Store) here should fix the issue

APK Creation Process:

Using Bubblewrap: https://github.com/GoogleChromeLabs/bubblewrap https://github.com/GoogleChromeLabs/bubblewrap/tree/main/packages/cli To create: bubblewrap init --manifest https://my-twa.com/manifest.json To generate assetlinks.json: bubblewrap fingerprint add <sha-256 fingerprint from Play Store>

[mekarpeles]

Theoretically done. Keys registered with olsystem https://github.com/internetarchive/olsystem/commit/4570982924249ae2f91bfa80a54492cc2e35e9fe

[RayBB]

@mekarpeles not theoretical anymore. Update just rolled out to me :)