For instance, when I first uploaded my expo app to the Apple App Store and Google Play, I didn’t include versionCode. But the second time I had to. And I got a CFBundleVersion error when uploading to iTunes Connect too. So I ended up having to spend over an hour building multiple times via exp, and multiple uploads with errors… just for some json validation. Seems like a waste of time for some obvious things.
For instance, for each of these keys, the documentation should have format. For instance - string or number.
I know there are some of these little threads online about how to fix these issues, but why debug when the documentation should just be more complete.
Here are the 3 I have issues with:
android: versionCode (integer, one greater than the last one uploaded)
ios:buildNumber (users don’t see this, and will be used as exactly what in the info.plist?)
version:
Again - all strings? numbers? decimals allowed? integers only?
Would be awesome to have a few json files with really great examples. Or even a JSON validator run before you run exp build:ios etc
hey, so it looks like you can add custom keys and values to the autogenerated info.plist file. the best place to see the syntax is probably documented by apple.
in a quick search i found this code example (under see the source code) which you can probably turn into a js object and be good