Problem
Sync profiles (.one/sync/profiles/*.json) contain a hardcoded connectionKey field. When a platform is re-authenticated via one add, the sync profiles still reference the old connection key, causing syncs to fail silently or return empty results.
Current behavior
// .one/sync/profiles/gmail_gmailThreads.json
{
"connectionKey": "live::gmail::default::d351509f...", ← stale after re-auth
}After one add gmail, the new key is ...ab499011... but the sync profile still points to the old key. Running one sync run gmail uses the stale key.
Expected behavior
Either:
- Sync profiles should reference the platform name (e.g.,
"platform": "gmail") and resolve the active connection at runtime
- OR
one add gmail should auto-update all sync profiles for that platform
- OR
one sync run should auto-detect when the profile's connection key doesn't match any active connection and warn/auto-fix
Impact
Gmail sync silently returns 0 results when the connection key is stale. The user sees no error — the sync appears to complete successfully but processes nothing.
Problem
Sync profiles (
.one/sync/profiles/*.json) contain a hardcodedconnectionKeyfield. When a platform is re-authenticated viaone add, the sync profiles still reference the old connection key, causing syncs to fail silently or return empty results.Current behavior
After
one add gmail, the new key is...ab499011...but the sync profile still points to the old key. Runningone sync run gmailuses the stale key.Expected behavior
Either:
"platform": "gmail") and resolve the active connection at runtimeone add gmailshould auto-update all sync profiles for that platformone sync runshould auto-detect when the profile's connection key doesn't match any active connection and warn/auto-fixImpact
Gmail sync silently returns 0 results when the connection key is stale. The user sees no error — the sync appears to complete successfully but processes nothing.