Sign-in works on my test version but not on the live site. Why?
Short answer
Check it was published as an app, not a website; then tell your AI exactly what happens when you sign in.
Deeper
Two addresses. While your app is built, you try it on your computer, at the address of its preview there. Once it is live, it is at https://<name>.pages.dev, where <name> is the name given to your site. GilbPlatform, the service that keeps your vaults, lets each address sign people in on its own: an approval for one does not cover the other. The live address gets its approval when it is published, with no request to the platform owner, but only for an app.
An app or a website. Two kinds of site. An app can sign people in and read and write vaults. A website cannot read or write vaults. Your AI publishes an app unless you say it is a website, and a name that was published as one kind cannot become the other. So if your site was published as a website, sign-in cannot work there. Ask your AI which kind it published. To fix it, the app must be published as an app under a new name; a new name is a new site, and uses one of your 2, and the name published as a website stays held and still counts as one of your 2.
How the live app signs people in. GilbPlatform's rule for published apps tells your AI to sign people in with GilbPlatform's ready-made sign-in code, the signin unit, version 0.2.7 or later, which uses the code sent by e-mail. No GilbPlatform sign-in cookie, the small note a browser keeps for a site, reaches the live app, so an app must not rely on one. Its pages may fetch data only from their own address and from GilbPlatform's own addresses, https://*.gilb.com. If your test version signed in some other way, tell your AI.
Signed in, but not for long. If people can sign in but must sign in again after every reload, or after a week, the app does not keep or renew the sign-in; the developer answer Why must my app's users sign in again on every reload, or after a week? tells your AI the fix.
From another computer. For an app, the connector keeps a key on the computer the app was published from; the platform lets the app sign people in with that key. Published again from another computer, the app gets a new key there, which takes the old key's place. If you can, publish updates from the same computer.
Switched off. If GilbPlatform switches publishing off for your account, your sites are no longer let sign people in, and a publish says Publishing for this account was switched off, so it cannot publish. Write to [email protected].
If the code does not come. The answer I did not get the code, or it does not work. What now? tells what to do.
Tell your AI. Say which address, which e-mail address you signed in with, what you did, and the exact words on the screen. Agent.Coder, the agent that writes your app's code, reads the browser's error messages itself with its browser tools, looks for the cause and works on a fix; a fix goes live only with your yes, published again under the same name. If your AI finds no cause in your app, write to [email protected] with the address and what you saw.
This answer is written for a computer screen.
Source: Standards read from GilbPlatform on 13 November 2026: Standard Rule_Code_deployment (RuleDeployPagesDev: No platform session cookie reaches the app. Do not rely on one.; Sign in with the GilbPlatformCode signin unit, version 0.2.7 or later; connect-src 'self' https://*.gilb.com; an ended entitlement gives not_entitled), Proc_v_i_c_PublishPagesDev (step 8: The platform admits exactly that origin for sign-in on its own.; step 10: an older signin does not renew), Agent.Coder (Browser; AskGoLive). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/routes/publish.ts:460-486 (an address is admitted only for kind app; a website's admittedOrigin is null); src/server/cors.ts (vault doors answer only admitted addresses); src/publish/records.ts:134-135 (Publishing for this account was switched off, so it cannot publish.), :201 (ended permission: sites Offline), :386-391 (a name cannot change kind); src/publish/admission.ts:1-9, :41-54 (a re-publish with a different key replaces the old approval; leaving Live revokes the approval). Connector 0.6.1, served at https://gilb.com/app/gilb-connector.mjs, read 13 November 2026: the app key per site name, made on a computer that has none. Live help pages, sentences shared: How does a browser app get the owner's approval? ("Each origin is approved on its own, so a second address, such as one you test on, needs its own approval."); How do I put my app or website live on the internet? (two kinds of site); How do I update my app after it is live? (from another computer); Why must my app's users sign in again on every reload, or after a week?; Why was my publish refused, and what do I do? (not_entitled); My app shows an error. What do I do?; I did not get the code, or it does not work. What now?
Checked against GilbApp d529620.