tauri-apps
Instructions regarding app signing
App signing is essential in order to upload an app to the play store.
In this commit I add specific instructions on how to use Java key store to sign the AAB file.
Deploy Preview for tauri-v2 ready!
Built without sensitive environment variables
| Name | Link |
|---|---|
| Latest commit | fd02bb127a3661dabad75eaff75c7a50f1391a5c |
| Latest deploy log | https://app.netlify.com/sites/tauri-v2/deploys/665e333c47a4bd00085e9daf |
| Deploy Preview | https://deploy-preview-2243--tauri-v2.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
Lighthouse |
1 paths audited Performance: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 92 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Thanks for contributing! We probably will wait until https://github.com/tauri-apps/tauri/pull/9964 lands as the instructions will change then.
9964 was closed but from the discussions emerged another signing guide: https://github.com/tauri-apps/tauri-docs/pull/2337 - it does not mention the play store though so i'd be open for suggestions on how to approach this (maybe just close this PR too and have the play store docs focus more on the rest of the publishing process)
