Repository navigation
Follow-up: OBACloud Live Activity pushes should preserve relevance-score #1252
Description
Context
PR #1243 (Problem 2 of #1189) sets a monotonic on-device relevanceScore so the Dynamic Island follows the newest Track. Aaron noted that OBACloud pushes still send a flat "relevance-score": 100 (see docs/LiveActivityPushNotifications.md), which re-ties scores after a push and undoes the Island ordering.
Ask
On the OBACloud / push side (onebusaway-cloud-services is archived for issues), either:
- omit
relevance-scoreon Live Activity updates so the on-device score is left alone, or - send a per-activity score that preserves newest-Track-highest ordering.
Tracking here so #1189 is not closed by the app-only PR alone.
Activity
Borisserz commentedon Sep 6, 2026
Docs/contract for omit-or-per-activity relevance-score (app already preserves on local refresh): #1403 — OBACloud still needs to stop sending flat 100.
Document omitting flat relevance-score: 100 on Live Activity pushes (#…
Merge pull request #1403 from Borisserz/fix/1252-relevance-score-push
aaronbrethorst commentedon Oct 16, 2026
I looked into this on the OBACloud side, and there's nothing to change. OBACloud already does option 1: it leaves out
relevance-score.Gorush#send_live_activity(app/lib/gorush.rb) and carries onlyevent,content-state,timestamp,priority, and optionallystale-dateanddismissal-date. It has never setrelevance-score; the field doesn't appear anywhere in the repo's git history.RelevanceScoreis a pointer in gorush, and it's only applied when it's set (notify/notification_apns.go). When it's left out, the APNs payload has norelevance-score, and the score the app sets on the device is left alone.The "flat 100" came from the sample payloads and the Node helper in
docs/LiveActivityPushNotifications.md, which #1403 already fixed. Thanks for tracking this, @Borisserz. Closing as resolved; this shouldn't block #1189.