Check the funnel beacon is accepted from a browser: sendBeacon sends credentials and utils/cors.ts sets no Access-Control-Allow-CredentialsDone
Wave

iOS — Settings, Analytics & tools build

Remaining build work across Settings, Analytics, ConnectCard, the AI panel, and QR/NFC programming. Everything marked 'coming soon' here is intended to ship.

TacTile › Launch TacTile › iOS › iOS — Settings, Analytics & tools build
60/133 done73 open1 open blocker
Selected taskclear

Check the funnel beacon is accepted from a browser: sendBeacon sends credentials and utils/cors.ts sets no Access-Control-Allow-Credentials

DoneOwner · Vivt_e9f24402

Found by the adversarial read of the public viewer audit (t_adc2145a). Repo reading only: not confirmed in a browser, no production read made. Every live /t page inlines a beacon that posts with navigator.sendBeacon (credentials included) to the API, and the API's CORS helpers never send Access-Control-Allow-Credentials, so a browser may refuse the post and the funnel may under-report from real phones.

Show the prompt
To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it