EVCharge E2E Verify — ELE-709

FAIL

Run ID: run-verify-ele-709-20260319-1127

Task: ELE-709 — КЛИЕНТ: СОЗДАНИЕ ЗАКАЗА: При только зарегистрированным пользователем, мои адреса пустые

Scenario: scenarios/fix-tests/verify-ele-709.md

Start: 2026-03-19 08:27:00 UTC

Finish: 2026-03-19 08:36:00 UTC

Duration: ~9 min

Steps

#	Module	Block	Status	Duration	Details
1	Client	Login and navigate to order creation	FAIL	~9 min	Client app stuck on loading spinner. Runtime error during Firebase initialization prevents app from loading.
2	Client	Verify hint text on "Мои адреса" tab	BLOCKED	-	Cannot verify — app did not load past splash screen.

Errors

Block 1: Client app initialization crash

Error: "Null check operator used on a null value"
Source: main.dart.js:91204 (after Firebase messaging initialization)

Console sequence:
1. TalkerService initialized
2. Firebase core initialized
3. Firebase messaging initialized
4. Firebase performance initialized
5. ERROR: "Null check operator used on a null value"
6. Telegram error notification sent

The app never progresses past the loading spinner.
Rebuilding the app (flutter build web --release) did not fix the issue.
The app environment points to PROD Supabase (api.zarady.ru).

This is an app-level bug unrelated to ELE-709.
The E2E test for ELE-709 cannot be executed until this initialization issue is resolved.

Screenshots

Step 1: Client app initial state — loading spinner (desktop viewport)

Step 2: Mobile viewport (430x932) — still loading spinner

Step 3: After full rebuild — same loading spinner

Code Analysis

Source code analysis confirmed that the hint text IS implemented in the Client app:

File: lib/create_order/create_order_page2_address/create_order_page2_address_widget.dart (line ~2427)

When lastAddresses is null (no saved addresses), the app shows:

"После того, как Вы сделаете первый заказ, здесь автоматически появится адрес из заказа и Вы сможете делать следующие заказы быстрее. Пока перейдите на вкладку "Указать на карте" и укажите адрес, куда приехать технику"

The code correctly checks recentAddressesVLastAddressesRow?.lastAddresses != null and shows the hint text in the else branch. The implementation appears correct, but visual verification could not be completed due to the app initialization crash.