Thank you, that was very helpful. Just one question:
Let's say I add something to my app which can't be published via OTA, like a barcode scanner. There I need to add permissions to "android" in app.json. So now I need to rebuild but as far as I know, rebuilding is also publishing. Does this mean, that users for example already get the new screens I added for the barcode scanner via OTA but can't use it as long as Google did not approve the new build I have to upload?
Tech Lead & Indie Hacker constantly testing new ideas. Keep learning by practicing, meeting people as well reading. Believe in execution more than anything else and want to evolve in a fast :)
Very good question, I had the same problem when upgrading the Expo SDK :)
Actually, the way I handle it is pretty simple. I just create another production channel.
Let's say my V1 is "prod-01", and I push my OTA when I don't need to add a feature like a barcode scanner for example.
Later, I need to add this feature where I need to have a new built. Ok then, I just create a "prod-02" channel, and this way, I now have 2 prod channels and the first one won't have this new feature until they upgrade the app on the Store.
I also have 2 git branches, one without the new feature and one with it so I can still push new improvements (which don't need a new build) to both channels :)
I hope it makes sense?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you, that was very helpful. Just one question:
Let's say I add something to my app which can't be published via OTA, like a barcode scanner. There I need to add permissions to "android" in app.json. So now I need to rebuild but as far as I know, rebuilding is also publishing. Does this mean, that users for example already get the new screens I added for the barcode scanner via OTA but can't use it as long as Google did not approve the new build I have to upload?
Or what will happen in this case?
Thank you.
Very good question, I had the same problem when upgrading the Expo SDK :)
Actually, the way I handle it is pretty simple. I just create another production channel.
Let's say my V1 is "prod-01", and I push my OTA when I don't need to add a feature like a barcode scanner for example.
Later, I need to add this feature where I need to have a new built. Ok then, I just create a "prod-02" channel, and this way, I now have 2 prod channels and the first one won't have this new feature until they upgrade the app on the Store.
I also have 2 git branches, one without the new feature and one with it so I can still push new improvements (which don't need a new build) to both channels :)
I hope it makes sense?