MyJackfruit

Help
Browse topics · Finishing

Finishing

← Finishing

A user cannot sign in to my app or did not get the code. How do I help?

Short answer

Ask them to check the e-mail address, use only the newest code and look in spam; if that fails, write to [email protected].

Deeper

You cannot sign a person in for them. GilbPlatform, the service that keeps the vaults, gives the maker of an app no list of the people who signed in to it, and GilbApp, the app where you use your vaults, has no screen for that, so you cannot look at their account either. You help by telling them what to check.

How they sign in. People sign in to your app with GilbPlatform, by a 6-digit code sent to their e-mail. GilbPlatform sends that e-mail through Resend, a US e-mail service. Its subject is Your GilbPlatform sign-in code, or the same with your site's name, the name in https://<name>.pages.dev, in place of GilbPlatform where GilbPlatform knows it. Your app's own screen may look different from GilbApp's.

The code did not come. Whether it lands in the inbox or in the junk or spam folder is decided by each person's e-mail provider, the company that runs their mailbox, not by GilbPlatform or by you, so no one can promise it. Tell them to look in the junk or spam folder too, and to check that they typed their e-mail address right. A code found in the spam folder works the same. A person can ask for a new code 45 seconds after the last one, and at most 3 times in 10 minutes for one address. From one network, at most 8 codes go out in 10 minutes, and 3 in 15 seconds. Past a limit no e-mail is sent, but GilbPlatform answers your app as if it were, so your app may still say a code was sent; the code they already have still works. After they sign in, the count for their address starts again.

The code does not work. A code works once, and for 10 minutes. Only the newest code they asked for works: asking again replaces the old one. A wrong code does not use the code up: they can type the right digits again. After 5 wrong codes the address is locked for 15 minutes, and longer each time it happens again, up to a day. The 5 wrong codes are counted for the address as a whole: asking for a new code does not start the count again. While it is locked, a correct code does not work either, so tell them to wait, then ask for a new code.

They forgot which e-mail they used. The sign-in screen does not say whether an address has an account. If they sign in with another address, they get a new account with its own first vault, the place where their records are kept, and do not see what they kept before: each address makes its own account. You could suggest they search each mailbox they use for an earlier e-mail whose subject ends in sign-in code: it went to the address they used. If that does not help, they can write to [email protected].

Changing the sign-in e-mail. A person cannot change the e-mail they sign in with themselves. Neither GilbApp nor id.gilb.com, GilbPlatform's own address, has a screen to change the e-mail address of an account, and GilbPlatform has no way to do it that you can reach yourself. If they need to change it, they write to [email protected]; nothing here promises what support can do. The answer Which e-mail address should I use, and can I change it later? says more, and I lost access to my e-mail. How do I get into my account? helps a person who can no longer open their mailbox.

When to write to support. If no code comes after they have waited and asked again, if the address stays locked, or if the people who use your app often miss the sign-in code e-mail, write to [email protected], and say when they tried. If no one at all can sign in, the fault may be in your app: tell your AI, as How do I tell my AI about a fault so it can fix it? shows, and see Sign-in works on my test version but not on the live site. Why? The answer I did not get the code, or it does not work. What now? shows the same code rules from a person's side, in GilbApp.

This answer is written for a computer screen.

Source: GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/auth/send-guard.ts:34-62 (45 seconds between sends; 3 per address and 8 per network in 10 minutes; 3 in 15 seconds); src/routes/email-auth.ts:349-420 (over a limit: no code and no e-mail, but the same answer, so nobody learns whether an address has an account); src/auth/email-otc.ts:63-76 (a code lasts 10 minutes; 5 wrong codes; locked 15 minutes, longer each time, up to 24 hours); src/auth/send-otc-email.ts:162-224 (subject Your … sign-in code with the app's name or GilbPlatform; sent through Resend); src/auth/otc-app-name.ts (an approved app is named by its registered name). Live help pages, sentences shared: How do I sign in with the e-mail code?; I did not get the code, or it does not work. What now? (the same code rules hold in an app built on GilbPlatform); Will my app's e-mails end up in spam? (Resend; junk or spam folder; A code found in the spam folder works the same.); Which e-mail address should I use, and can I change it later? (no screen to change the e-mail; write to [email protected]; each address makes its own account); Can I see who uses my app? (no list of the people who signed in); Can my app have its own users who sign in?

Checked against GilbApp d529620.