Repository navigation
Conversation
…Settings Xcode 16's SDK doesn't mark UNNotificationSettings Sendable, so awaiting notificationSettings() from the main actor failed the Swift 6 build in CI. Read the settings through the callback API and return only the mapped permission status. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Note Review skipped Codemetrics is installed on this repository, but it hasn't been added to your team yet. To enable AI code reviews for this repo, go to your dashboard and add FridgeLuck to your team's repositories. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughNotification status lookup now uses a shared callback-based helper. Pending notification retrieval now returns identifiers, which the scheduler uses to reconcile stale notifications. ChangesNotification status retrieval
Pending notification identifiers
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~8 minutes Change: Refactor Merge Risk: ⚪ Minimal · up to The notification-status and pending-cleanup changes preserve the inspected behavior. No material merge blocker remains; normal CI checks should still run. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The scheduler only needs identifiers, and Xcode 16's SDK doesn't mark UNNotificationRequest Sendable, so returning requests to the scheduler actor failed the Swift 6 build in CI. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ionSettings Folds fix/notification-settings-sendable @ 8540848 into the app integration trunk, fold 10 of 12. Co-authored-by: obvious-autobuild[bot] <262744130+obvious-autobuild[bot]@users.noreply.github.com>
What changed
maindoesn't build in CI. On the runner's Xcode 16.4 (iOS 18.5 SDK), Swift 6 checking rejects notification-center results that cross actors, because that SDK doesn't mark them Sendable:AppPermissionCenterreads notification settings throughgetNotificationSettings. It maps them toAppPermissionStatusinside the callback, so only the Sendable status crosses actors. The status check and the permission request share that helper.UserNotificationCenterClientnow returns pending identifiers ([String]) instead ofUNNotificationRequests. The scheduler actor only ever read the identifiers. The test mock follows the new method.Behaviour doesn't change.
Why
Every PR's
build-and-testjob fails on these errors before any test runs; the lastmainrun, on 1f85e88, failed the same way. #4 and #5 need a buildingmainto get simulator results.Verification
Risk
Checklist
Summary by CodeRabbit