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

brilliantlabsAR / noa-flutter

The Noa app for iOS and Android

Other

30 stars 20 forks source link

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

Open elimisteve opened 3 months ago

elimisteve commented 3 months ago

I got key signing errors without doing this!

elimisteve commented 3 months ago

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 commented 3 months ago

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!