wodin
November 18, 2019, 2:43pm
6
Hi
I haven’t thought about this as much as you (or @llamaluvr ) have, but one thing that might help is publishing to some sort of staging release channel and then promoting it to production when you’re ready for it to be made available to the users.
See also:
Whether this is the “best” practice is in the eyes of the beholder, but what I’ve ended up doing is keeping a separate version number just for my JavaScript bundle. I have a simple file called build.json that has a single property:
{
"jsBuildNumber": 1
}
Then, I have a node.js script that wraps expo publish, incrementing the build number just before publishing:
const shell = require('shelljs');
const jsonfile = require('jsonfile');
const file = 'build.json';
const data = jsonfile.readFileS…
SDK version will lock your OTA updates to a particular version only if you’re upgrading your Expo SDK every time you’re putting a new native version in the store. If you change native dependencies without upgrading the Expo SDK, then checking the SDK version will not be help.
Release channels (more info in the Expo docs) can be a great help with this, I’ve found. I’ve started naming my release channels for a) my API server the build is pointing to, and b) the minimum native build number that w…