[BUG] pg login loop on new funded account — "mapping not ready yet"; misleading "✓ setup complete"

[ottovlotto]

Severity: Critical (modding path) · P0
Reported by: DevEx Audit (External) / DevCult
Source: W3S PG Audit v3 (External) by DevCult, 16 June 2026.
Surface: CLI v0.39.1 (Linux), pg login with a new funded account.

Symptom

pg login loops on a fresh funded account:

✕ mapping not ready yet
Your account isn't ready for smart contracts yet — this usually resolves on its own. Wait a minute, then run playground login again. If it keeps failing, run playground logout, then playground login and approve the allowances on your phone.

The suggested logout → login does not help.

Separately: it's bad practice to print "✓ setup complete" while giving no detail/logs about what actually failed, leaving the user stuck in a loop.

Notes

The misleading-success half overlaps closed #316 ("Installer reports 'setup complete' even when a step errored") — but that was installer-scoped; this is pg login. The "mapping not ready" loop on a fresh funded account is not otherwise tracked.

Recommended fix / next steps

• Fix / diagnose the AssetHub mapping "not ready for smart contracts" loop on funded accounts; make logout→login actually recover.
• Don't print "✓ setup complete" when a step failed — surface what failed and the logs.

[ottovlotto]

didn't manage to reproduce - not happening every time - have downgraded to P1 unless we see it again

[UtkarshBhardwaj007]

++ to @ottovlotto - can't reproduce. Would be good to see trace logs from the CLi and phone logs immediately after this happens