Where "login" actually lives
This is the part that surprises people coming from Expo, so it is worth stating plainly.
EAS has accounts because it is a hosted product serving thousands of organizations; the login proves which tenant you are. leas runs on your own hardware and your own GitHub, so there is no tenant to identify. Your identity is your credentials. Whoever holds the five files below can ship as you. Section 12 covers what adding real accounts would take.
So "changing our login" always means one of two concrete things: rotating one of these five credentials (section 8), or moving to a different Apple team or Play account (section 9). Here is what each one is and what it costs you if it leaks.
| Credential | What it proves | Lifetime | If it leaks |
|---|---|---|---|
iOS distribution certificatedist.p12 |
Builds signed with it came from your Apple team. | About a year. | Serious. Someone can sign software as you. Revoke it in the Apple developer console immediately — accepting that every profile built on it dies with it. |
Provisioning profile.mobileprovision |
That certificate may ship that specific app. | About a year, or the instant its certificate is revoked. | Minor on its own — it is useless without the private key. |
App Store Connect API keyAuthKey_*.p8 |
You may act on App Store Connect with a given role. | No expiry. Lives until revoked. | Serious. Someone can upload builds and edit your store listing. Revoke and reissue. |
Android upload keystoreupload.keystore |
This bundle genuinely came from you. | As generated — 10,000 days above. | Recoverable. Request an upload key reset through Play Console support. |
Play service account*.json |
You may publish to these Play apps. | No expiry. Lives until the key is deleted. | Serious. Delete the key in Google Cloud and revoke the account in Play Console. |
Every one of these is a bearer credential: possession is authorisation. There is no password on top, no second factor, no per-person audit trail. That is precisely why a real multi-tenant product needs a credential service rather than a folder — see section 12.