Repository navigation
[Bug]: iOS: an environment that is switched off can't be opened, so a failing T3 Connect environment can't be removed #18719
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/mobile (iOS)
Steps to reproduce
- Have a T3 Connect environment that fails its health check. Mine shows "Managed endpoint health request failed. Trace ID: …".
- Switch it off in Settings → Environments. That's the natural thing to do with an environment that can't connect.
- Tap the row's chevron to open its settings and remove it.
Expected behavior
The settings for an environment open whether it's on, off or failing, so you can remove it from the phone. Alternatively, the expanded error state could offer a Remove action directly.
Actual behavior
While the row is off, its chevron is greyed out and does nothing. The expanded error state shows the message and trace ID but no Remove action. That leaves no way to remove the environment from this screen.
On the same screen, a T3 Connect environment that was switched on but failing ("Failed to connect. Reconnecting…") still had an active chevron. So the chevron appears to follow the on/off switch rather than the error, and the only way into an errored environment's settings is to switch it back on, which isn't obvious.
Account → T3 Connect → Deregister (see #17043) isn't a substitute. It removes the environment from the account for every device, not from this phone.
Related but different: #12012 / #18228 (the trash button on a saved direct environment does nothing).
Impact
Cosmetic to moderate. A dead entry with a red error stays in the Environments list for good.
Version or commit
Server 0.0.45 (stable). iOS app from the App Store, current as of 2026-10-12.
Environment
iPhone with two environments on one Mac (two t3 serve instances with separate base dirs). Both are reachable over Tailscale and are T3 Connect linked.
Activity
juliusmarminge commentedon Oct 12, 2026
Note
Grok responding on behalf of Julius.
Thanks for the detailed report. On current
main, the row you're describing doesn't look like a saved environment that was switched off. It looks like a discovered T3 Connect registration that has never been saved on this phone.ConnectedCloudEnvironmentRowinapps/mobile/src/features/connection/CloudEnvironmentRows.tsx) can always be tapped to open its settings, whether it's on, off or failing, and its chevron stays full strength. Long-press removes it from this device. When it's off, it shows "Off" and hides the health error.CloudEnvironmentRow) shows the relay's health error, such as "Managed endpoint health request failed", next to an inert chevron at 40% opacity. That matches your description. There's nothing to remove locally because it isn't stored on the device. It comes from your account's registrations, so making it go away means deregistering it from the account. Hiding one registration on a single device is tracked in Manage T3 Connect environment names and registrations #13057.Could you check two things?
Also note that the App Store build can lag
main(see #14282), so a screenshot of the row would help confirm which case this is.grahamfarrar commentedon Oct 14, 2026
Thanks, that's the case.
https://mac-studio…:8444/and:8445/), and both are connected. The T3 Connect section lists the same two servers as discovered registrations: "Glass House (Studio)" shows "Available · Relay online", and "Graham's Mac Studio" shows "Managed endpoint health request failed. T…". Both rows have their switch off and a dimmed chevron. I never turned the failing one off myself; my original steps were wrong about that.So this is the discovered-row case. There's nothing to remove on the phone, and #13057 covers hiding it on one device. I'm fine with closing this in favor of that one.
One open question: why does that registration fail its health check while the other server on the same Mac reports its relay online? The server behind it is up and works over Tailscale. I'll look at that separately and open a new issue if it's a bug.
t3dotgg commentedon Oct 21, 2026
Note
🤖 Claude Opus 5.5 responding on behalf of Theo
Thanks for the report. Issue #13057 already tracks this problem, so we close this issue to keep all detail in one place. Please follow #13057 and add your version and steps there if they differ. Please do not open a new issue for the same problem.