Repository navigation
Description
Before submitting
- I searched existing issues. Related reports are listed below; I did not find this exact iOS TestFlight case.
- I included the observed behavior, reproduction attempts, versions, and redacted diagnostics.
Area
apps/mobile (iOS notification registration / relay delivery)
Summary
Ordinary completion notifications have never worked on this iPhone. The app can load and use the affected conversation. After enabling the Mac's separate Publish agent activity setting, a Live Activity appeared, but ordinary notifications still did not arrive. They also failed in a second test with Live Activity Updates off and Device Notifications on.
Two direct, environment-signed diagnostic sequences were accepted by the production relay with HTTP 200 and ok: true, but returned deliveries: [] for both running and completed states. Reopening the mobile app did not change that result. The precise reason for selecting no deliveries is not established.
Version or commit
- iPhone: T3 Code Mobile 3.0.0 (198), installed through TestFlight. The supplied TestFlight screenshot lists a release date of October 27, 2026. The user reports using the latest available TestFlight build; availability of newer builds was not independently checked.
- Mac desktop / bundled server at initial diagnosis: 0.1.4-nightly.20261027.3796.
- Local source inspected for diagnostic leads:
eb751fa0730d6a51d56547cb7fcaf4822a7e0e3b. This is a source reference, not a verified mapping to the installed iPhone binary or deployed relay. - Investigation date: October 28, 2026.
Environment
Native T3 iPhone app connected to a macOS arm64 desktop environment with T3 Connect enabled. The iPhone can load the same conversation. Mac: macOS 27.0.1 (26A434). Exact iPhone model and iOS version were not recorded.
Settings verified
User-supplied screenshots show:
- iOS Allow Notifications on, with Lock Screen, Notification Center, and Banners selected; Sounds and Badges on.
- In-app Device Notifications and Live Activity Updates initially on.
- TestFlight build identity 3.0.0 (198).
The Mac's Settings → Sharing & access → Publish agent activity was initially off. It was enabled through the desktop UI and the saved value was verified as true. That resolved the initial absence of Live Activities, so the remaining report is about ordinary notifications after publishing was enabled.
Steps to reproduce / observed tests
This is reproducible on the reporting installation; a clean-install reproduction has not been established.
- Use the native TestFlight app with notification permission and Device Notifications enabled; connect to the desktop environment and enable Publish agent activity on the Mac.
- Start an agent turn, background the iPhone app, and lock the phone. In the first controlled test the turn waited approximately 30 seconds before finishing.
- A Live Activity appeared. No ordinary notification was received. The user explicitly confirmed the phone remained locked / T3 remained in the background when the turn finished.
- Turn Live Activity Updates off, keep Device Notifications on, and repeat the delayed completion test. No ordinary notification was received.
- Fully close and reopen T3, leave it open for at least 15 seconds, then repeat the relay diagnostic below. Delivery selection still returned an empty array.
Expected behavior
With notification permission, Device Notifications, environment publishing, and the relevant cloud notification preferences enabled, a newly completed turn should produce a completion alert while the iPhone app is backgrounded. If push registration or cloud preferences prevent delivery, setup should expose that failure.
Actual behavior
No completion notification arrived in either controlled test. Live Activities worked after enabling environment publishing. Reopening T3 did not restore ordinary push delivery.
Logs or stack traces
Local server traces recorded agent activity publish deferred pending confirmation, followed by agent activity deferred publish confirmed for the actual test conversation, with statePhase: "completed". Example confirmation timestamps: 2026-10-28T20:27:23.206Z and 2026-10-28T20:35:36.482Z.
Separately, a diagnostic script used the existing environment credential and environment Ed25519 signing key locally to call:
POST /v1/environments/<environmentId>/threads/<diagnosticThreadId>/agent-activity
For each diagnostic sequence, a fresh temporary thread ID was used, with signed running and completed states, followed by a null state to remove the diagnostic row. The regular conversation and its messages were not modified by this probe. The same results were observed before and after reopening the iPhone app:
{"phase":"running","status":200,"ok":true,"deliveries":[]}
{"phase":"completed","status":200,"ok":true,"deliveries":[]}
{"phase":"cleanup","status":200,"ok":true,"deliveries":[]}The diagnostic phases were sent consecutively; this supplementary probe is not a substitute for the separate real, delayed agent-turn tests. An empty delivery array establishes only that the relay returned no delivery results for those requests. It does not prove which registration, preference, token, or delivery-policy condition caused that outcome, or demonstrate an APNs rejection.
No credentials, signing keys, push tokens, account identifiers, private relay hostname, or full local traces are included in this public report.
Investigation leads / requested maintainer checks
Please inspect the reporting account's cloud environment-link notification preferences and iPhone device registration: whether an ordinary push token is present, the device's stored notification preferences, APNs topic/environment, and the reason no delivery results were selected.
There is a related source-level diagnostic gap: nativePushTokenRegistration in remoteRegistration.ts can convert a native token-fetch failure into a tokenless registration with notifications disabled. A relay-accepted registration can still be treated as registered by the settings UI. This is a plausible lead, not a confirmed cause on this iPhone; no native iPhone logs or production registration records were available.
Related issues
- Android push-token failures are reported as successful notification registration #26530: Android push-token failures reported as successful registration. Related registration handling, different platform; its missing-Firebase diagnosis is not asserted for this iOS build.
- [Bug]: iOS 1.0.3 cannot exchange relay DPoP access token (invalid_dpop) — T3 Connect, notifications, and Live Activities all fail #7170: older iOS DPoP exchange failure. Not established here; the app loads the conversation and a Live Activity worked.
- Unify mobile notification delivery diagnostics across APNs and FCM #10863: broader notification-delivery diagnostics.
Impact
Major degradation or frequent failure: completion alerts cannot be relied on when away from the desktop.
Workaround
Enabling Publish agent activity restored Live Activities. No working workaround for ordinary notifications was found. Disabling Live Activity Updates and closing/reopening the iPhone app did not resolve it.
Activity
kukitch commentedon Oct 31, 2026
Same symptom here, with a pending question rather than a completion, plus a note on where the Publish agent activity switch can (not) be reached.
Setup: T3 Code 0.1.5 on three Macs (one desktop app acting as its own server, two headless
t3 servebackground services) and one Linux server, linked to each other. iPhone app with Device Notifications and Live Activity Updates on; iOS Settings for T3 Code allow notifications with Lock Screen, Notification Center, Banners, Sounds and Badges.Five tests on 2026-10-31, each an agent thread that asked the user one question with the question tool and waited:
delegate_taskchild on the same headless server: no phone notification.Where the switch is:
t3 serveserver, Settings > Sharing & access > This machine says "No environment selected", even though the server is listed and Connected under Environments. The settings search entry for "Publish agent activity" is marked local-environment-only, so it never appears for those servers.Desktop notifications on the Mac whose app is its own server do appear ("Input needed" with the thread title), but they seem to pop up when the user sends a message rather than when the thread starts waiting, which may be a related ordering problem.
Expected: a pending question or approval from any thread, including delegated tasks and threads on linked or headless servers, notifies the phone when no desktop client is in the foreground; and headless servers have a way to enable agent-activity publishing (a setting in their web client or a
t3CLI flag).tunds commentedon Nov 11, 2026
Another report of the same: on iPhone (iOS 27) I receive no push notifications for thread activity — no completion notifications for runs finishing, and none for delegated sub-agent threads that finish or need input — while the desktop host is running and the phone is linked. Happy to provide redacted diagnostics if you tell me where to collect them.
ristoxy commentedon Nov 12, 2026
Additional evidence for the missing completion alerts on v0.1.8 (
bf469bb19669671d0df2efda74ed73867a7137c0).Reproduction reported from our setup:
t3 connect link --publish-onlyand enable activity publishing.Expected: a completion notification for the finished thread. Reported host diagnostic:
deliveries.total=0.CloudLinkhardcodesliveActivitiesEnabled: true.AgentActivityPublishertherefore supplies the user-wide aggregate;notificationForAggregateexamines onlyactivities[0], which can be the other running thread. An isolated source-function test returnsnullwith concurrent work and a push when the completed thread is alone, on this tag and mainfc2b5de20cb572d2333e03284466e3c804d25c84; APNs was not retested.Could fallback alerts select the published thread? Alternatively, expose
--notifications-onlyor honor the device preference without enabling tunnels. The phone cannot change the link withoutrelay:write; its relink currently requests managed tunnels.Related: #11073 (closed, unmerged), #15015 and #32779 (open).
Written by Hermes Agent (GPT-6.1 Sol), reviewed by a human before posting.