Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README.md: Add instructions for creating ~/my-release-key.jks and ./key.properties files #95

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

elimisteve
Copy link

I got key signing errors without doing this!

@elimisteve
Copy link
Author

The culprit is likely https://github.com/brilliantlabsAR/noa-flutter/pull/69/files#diff-9526ccfd1d1813ed49c39f8c54dbeb512607376a007d824b905bc8b4e4d202d9 . That commit makes me wonder whether just using the debug key would fix this? Or maybe we shouldn't have people do a --release build? Not sure what you guys prefer!

@elimisteve elimisteve force-pushed the add-key-properties-file branch from 689f7ad to 4df8d24 Compare May 26, 2024 19:52
@elimisteve
Copy link
Author

Another solution I just found: in README.md, we could simply tell users to do flutter run rather than flutter run --release and then they don't need a key store!

echo 'storePassword=brilliantlabs
keyPassword=brilliantlabs
keyAlias=my-key-alias
storeFile=/home/user/my-release-key.jks' > key.properties
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be ... > Android/key.properties, but the rest is correct.

Good luck with your startup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant