> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/account/qr-sign-up.md).

# Sign up by QR invitation

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/account/qr-sign-up.md).
{% endhint %}

Someone with a QR invitation link creates a Snapfix profile in three steps: their name and email or phone number, a password, then a screen that asks them to open the verification link sent to that email or phone.

* **Where:** iOS and Android: a link of type `qrcode-invitation`, while signed out. The link comes from a QR code shared from a group ([Group QR codes](https://docs.snapfix.com/how-the-apps-work/screens/groups/qr-codes.md)). Android also opens it from the onboarding link that carries a first name, last name and email. A signed-in iOS user who opens the link stays where they are (ios @ aa31967ac8, `Managers/DeepLink/DynamicLinkContextDeeplinkHandler.swift:251`); see [Deep link](https://docs.snapfix.com/how-the-apps-work/screens/account/deep-link.md).
* **Who:** signed-out people with a QR invitation.
* **Feature:** [Joining a site](https://docs.snapfix.com/product/features/onboarding/join-site.md)

iOS: `SignupProfileVC`, then `SignupPasswordVC`, then `SingupSuccessVC`. Android: `RegistrationNewActivity` with `RegistrationProfileNewFragment`, `RegistrationPasswordNewFragment` and `RegistrationVerificationFragment`.

```mermaid
flowchart TD
  link["QR invitation link"] --> s1["Step 1: name and contact"]
  s1 -->|"contact already has an account"| alert["Alert: account exists"]
  s1 -->|"Next"| s2["Step 2: password"]
  s2 -->|"Next: generate-verification-f3d8x-v11"| ref["Server sends the verification link, returns a reference"]
  ref --> reg["reg-f3d8x-v11 stores the form (iOS: at once; Android: when step 3 opens)"]
  reg --> s3["Step 3: check your email or text message"]
  s3 --> mail["Person opens the verification link"]
  mail --> done["dl-ctx for verify_profile creates the account"]
```

## Layout

Both apps show a step count in the top right ("1/3", "2/3", "3/3"). Android also shows a stepper bar under the logo.

**Step 1, profile.**

* iOS: "Sign up to get started!", "Your first name", "Your last name", "Registration Type" with "Email" and "Phone Number", the matching field (phone with a country picker), "Next". Below: Google, Apple and Microsoft (Azure) buttons, the Google API policy line from [Sign in](https://docs.snapfix.com/how-the-apps-work/screens/account/sign-in.md), "Data Policy" and "Having trouble logging in? HelpHub.".
* Android: "Sign Up to Get Started", "First Name" and "Last Name" (hints "Your first name", "Your last name"), "Registration Type" with "Email" and "Phone Number", the matching field, the Google, Apple and Microsoft buttons with the Google data-use notice, "Next", and "HelpHub.".
* Neither app shows a profile photo on this step. Android's fragment still has a camera-or-gallery picker, but its layout has no view that opens it.

**Step 2, password.**

* iOS: "Set Your Password", "Password", "Confirm password", four rule lines that tick when met ("At least 8 characters", "At least 1 number", "At least 1 uppercase letter", "At least 1 lowercase letter"), "Next", and "By signing up you agree to our terms of service & fair usage policy." with links.
* Android: "Set Your Password", "Password", "Confirm Your Password", "Your password must include" with a tick per rule, the checkbox "Snapfix can send me account details and periodic product updates via email or SMS.", "By signing up you agree to our terms of service & fair usage policy." with links, and "Next".

**Step 3, check your email or phone.**

* iOS (`SingupSuccessVC`): "Verify Your Email" or "Verify Your Phone Number", "An email has been sent to:" or "A SMS has been sent to:", the address, "Make sure to check your Spam/Junk folder and click the link in the email to verify your profile." (for a phone, "…in the phone number…"), and a back arrow.
* Android: "Verify your email" or "Verify your phone", "An email has been sent to:" or "A SMS text message has been sent to:", the address, and for email the same spam hint. The layout also holds a six-digit code field, "Resend verification code", a resend timer, "Complete Registration" and a terms line, but all of them are hidden and nothing in the code shows them (android @ 86068bfeea, `res/layout/fragment_registration_verify_otp.xml`).

## Inputs

| Field                     | Type                      | Required                | Default                                       | Rules and messages                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| ------------------------- | ------------------------- | ----------------------- | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| First name                | Text                      | Yes                     | Empty; on Android the onboarding link's name  | iOS: "Next" stays disabled until both names and a valid contact are filled. Android: "Please enter your first name".                                                                                                                                                                                                                                                                                                                                                                                                                               |
| Last name                 | Text                      | Yes                     | Empty; on Android the onboarding link's name  | Same as first name. Android: "Please enter your last name".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| Registration Type         | "Email" or "Phone Number" | Yes                     | "Email"                                       | Switching clears the contact field.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| Email                     | Email                     | Yes, for "Email"        | Empty; on Android the onboarding link's email | Must be a valid address and not end in ".com.com" (iOS). Android: "Please enter an email address", "Please enter a valid email address".                                                                                                                                                                                                                                                                                                                                                                                                           |
| Phone                     | Phone with country picker | Yes, for "Phone Number" | The device region's code                      | iOS: not letters only, and must parse for the chosen country. Android: "Please enter valid phone number".                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| Password                  | Password                  | Yes                     | Empty                                         | Rules: 8 or more characters, one number, one uppercase and one lowercase letter. Android also refuses spaces and enables "Next" only when every rule passes and both fields match; errors "Please enter a password" and "Your password does not yet comply with our security requirements. Please adjust.". iOS enables "Next" when the password is not empty, the two fields match and it contains a number: the other rules only change their tick, so a one-character password with a digit passes. The server does not check the rules either. |
| Confirm password          | Password                  | Yes                     | Empty                                         | Must match the password.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| Product updates (Android) | Checkbox                  | No                      | Off                                           | Sent as `account_and_product_updates`. iOS has no control and always sends 1 \[[ASK-27](https://github.com/snapfix/docs/blob/main/ASK.md#ask-27-where-do-users-change-their-communication-consent-and-how-should-it-be-stored)].                                                                                                                                                                                                                                                                                                                   |

Android also sends `onboarding_code` from a field on the profile step, but that field is hidden, so the value is empty.

## Actions

| Action                            | Who                  | What happens                                                                                                                                                                                                                                                                                                             | API                                                                                                                                   |
| --------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
| "Next" (step 1)                   | Anyone with the link | Checks that the email or phone is free. If it is taken, shows the account-exists alert and stays. Otherwise opens step 2.                                                                                                                                                                                                | iOS: `POST /validate-username`; Android: `validate_username` ([Auth API](https://docs.snapfix.com/engineering-reference/api/auth.md)) |
| Google, Apple, Microsoft (step 1) | Anyone with the link | Signs up with the provider instead of the form, sending the invitation token with it.                                                                                                                                                                                                                                    | `/sso-google`, `/sso-apple`, `/sso-azure` on [Auth API](https://docs.snapfix.com/engineering-reference/api/auth.md)                   |
| "Next" (step 2)                   | Anyone               | Sends the name, contact, invitation token and device data, encrypted. The server checks the contact and the invitation, sends an email or SMS with a verification link, and returns a reference (authpy @ 5d5758661c, `model/feature_user_auth.py:1494-1597`). iOS then sends the form at once (below) and opens step 3. | `POST /generate-verification-f3d8x-v11` on [Auth API](https://docs.snapfix.com/engineering-reference/api/auth.md)                     |
| Back (steps 1 and 2)              | Anyone               | Returns a step.                                                                                                                                                                                                                                                                                                          | -                                                                                                                                     |
| Back (step 3, iOS)                | Anyone               | Runs the app's log-out, which leaves the sign-up.                                                                                                                                                                                                                                                                        | -                                                                                                                                     |
| "HelpHub." / support              | Anyone               | Opens [Help with logging in](https://docs.snapfix.com/how-the-apps-work/screens/help/login-help.md) or an email to support.                                                                                                                                                                                              | -                                                                                                                                     |

**Registration request.** iOS sends the stored form to `reg-f3d8x-v11/{reference}` as soon as step 2 succeeds; Android sends it when step 3 opens. The server only stores the form on the verification link, including the password in plain text, and answers "User registration is under verification." (`app.py:1217-1244`). iOS makes this request with the shared login. Both apps encrypt the code request with a time-based code made from a secret in the app.

* On iOS, a failed registration request shows nothing.
* On Android, a success answer is treated as a finished sign-up: the app saves the tokens and user from the answer and opens Home, or the not-invited flow when the user must create a business (`RegistrationNewActivity.java:543-551, 845-882`). The answer carries no tokens or user, so what the person sees next is unclear \[[ASK-66](https://github.com/snapfix/docs/blob/main/ASK.md#ask-66-what-does-android-show-after-the-qr-sign-up-registration-request)].

**Verification link.** The email or SMS holds a link to `dl.snapfix.com`. Opening it sends the link to `dl-ctx`, which creates the account from the stored form and marks the invitation used (`model/feature_token_ops.py:3598-3612`). See [Deep link](https://docs.snapfix.com/how-the-apps-work/screens/account/deep-link.md) and [Account access](https://docs.snapfix.com/how-the-apps-work/screens/account/account-access.md).

**Resend (Android, hidden).** The code would send the reference to `resend-code-mobile-91r7o-v10`. The server looks the reference up in the wrong table and answers "invalid reference". The control is hidden, so nobody reaches it today.

## States

* **Loading:** a progress indicator while a request runs. On iOS the username check shows it with no text.
* **Empty:** "Next" stays disabled until the step is valid.
* **Error:** an alert with the server's message. A failed username check on iOS shows "Something went wrong. Please try again." with "Ok". Android shows "Something went wrong. Please try again after sometime." when its encryption key is missing.
* **No permission:** none; the person is signed out.
* **Offline (mobile):** both apps check the connection before each request, show an alert and send nothing.

## Dialogs and sheets

* **Account exists, step 1:** "An account exists for this email." (iOS hard-codes this title for phone numbers too) with "Please go to the login screen to login, or contact <customersupport@snapfix.com> for assistance." and "Ok". Android shows the same text, with a phone version.
* **Account exists, step 2:** when the code request says the contact is taken, iOS shows a custom alert "A Snapfix account already exists for …" with a reset option, and Android a dialog "A Snapfix account already exists for" the address, "Don’t know or forgot your password?" and a "reset password" link. Both open [Forgot password (legacy)](https://docs.snapfix.com/how-the-apps-work/screens/account/legacy-reset.md).
* **Channel sheet (Android):** a sheet to pick SMS or WhatsApp exists, but it only opens when `IS_WHATSAPP_OTP_ENABLED` is on. That flag is off, so a phone always gets an SMS.

## Platform differences

* **Step 3:** iOS shows a separate screen whose only way out is a back arrow that logs out. Android stays in the same activity and sends the registration when the step opens.
* **Step bar:** both show "1/3" to "3/3"; only Android has a stepper bar.
* **Password rules:** Android enforces all rules and refuses spaces; iOS only checks for a number.
* **Product updates:** Android has the checkbox; iOS sends 1 \[[ASK-27](https://github.com/snapfix/docs/blob/main/ASK.md#ask-27-where-do-users-change-their-communication-consent-and-how-should-it-be-stored)].
* **Onboarding link:** only Android accepts the link with a prefilled name and email.
* **Web:** sign-up is not offered. What a QR invitation does when opened in a desktop browser is open \[[ASK-42](https://github.com/snapfix/docs/blob/main/ASK.md#ask-42-are-qr-invitations-meant-for-phones-only)].


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/how-the-apps-work/screens/account/qr-sign-up.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
