Per-project Expo account
complete
Sébastien Lorber
Hi,
I work on multiple Expo projects which have to be published by different users. Let’s say I work on Expo projects for Company1 and Company2.
Currently it seems it’s only possible to be logged to a single Expo project.
Unfortunately it is easy for me to forget checking my current Expo login, and publish the project of Company2 under the name of Company1 for example.
I’d like to know how to prevent this issue?
I think it would be useful, in app.json, to be able to specifiy the account under which the project should be published and offer some kind of login switching system or at least block publishing without --force if current login is not the one found in app.json
See initial forum post: https://forums.expo.io/t/using-multiple-expo-accounts/5349
Kim Brandwijk
complete
This is now possible using the
owner
field in your app.json
. See the app.json reference for more information.Kim Brandwijk
complete
This is now possible using the
owner
field in your app.json
. See the app.json reference for more information.Miklós Fazekas
FWIW there is a simple implementation of this feature at: https://github.com/expo/expo-cli/pull/429
Scott Carpenter
This would be EXTREMELY helpful. I publish apps for multiple clients, and it's a nightmare having to switch back and forth between users every time I switch projects.
arcom
Yeah this is vital. Some sort of "organization" accounts where you can invite other devs, which gives them access to push to XYZ endpoint. Maybe this is somewhere expo can monetize.
Kyle Welch
This would be very helpful not only to consultants working on multiple project for different teams, but the enterprise benefit from this would be substantial. I think one service that did a great job with structuring for enterprises is NPM, they have executed much better than I would be able to describe.