# Mobile bug reports — LangSide: Learn English

Environment: iPhone 17 · iOS 26.5 · TestFlight v1.1 (build 1) · Simulator: iPhone 14 Pro Max, iPhone 16 Pro, iPhone 17 Pro

Two confirmed defects. No sample tickets.

## BUG-IOS-001 — Password validation rules differ between the iOS client and backend

**Type:** Validation / Functional  
**Severity:** Medium  
**Priority:** Medium

**Preconditions:** Registration screen is open. Swagger UI is available.

**Steps:**
1. On iOS, enter a valid email and a 4-character password (e.g. `Ab12`)
2. Submit registration — the client shows an alert: password must be at least 8 characters
3. Send the same payload to `POST /api/v1/auth/register` in Swagger UI

**Expected:** The same password rule on client and server. If the UI requires 8 characters, the API rejects a 4-character password.  
**Actual:** The backend accepts a 4-character password that the iOS client rejects.

**Finding:** Client-side validation and server-side validation enforce different password requirements.

## BUG-IOS-002 — User can select multiple answers before the onboarding screen advances

**Type:** UI / Logic  
**Severity:** Medium  
**Priority:** Medium

**Preconditions:** Onboarding shows a single-choice question. After a tap, the screen waits about 1.5 seconds before moving on.

**Steps:**
1. Open an onboarding question with one expected answer
2. Tap the first option
3. Before the automatic transition, tap a second option
4. Check the selected state

**Expected:** After the first tap, other options lock. Only one answer is kept.  
**Actual:** During the delay, a second option can still be selected. Two answers can look selected at once.

**Risk:** Rapid interaction during the transition can leave the onboarding state ambiguous.