Project

General

Profile

Actions

Feature #71

open
VJ

Verify and implement iOS meal reminders; resolve platform rule conflicts

Feature #71: Verify and implement iOS meal reminders; resolve platform rule conflicts

Added by Vince Jurić 11 days ago.

Status:
To Do
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Imported from GitHub issue 242.
Source labels: enhancement, needs-info, ios.
Original state: open. No source milestone.

Problem

Issue GitHub 233 requires all future meal reminders through Day 30 while the app remains closed.
A valid plan with three distinct daily starts requires 90 notifications.
Apple documents 64 pending notifications for the deprecated UILocalNotification API.
Current UserNotifications capacity requires verification on supported iOS versions.
Background tasks cannot guarantee replenishment after the user closes the app.

Scope

Verify iOS capacity and implement a device-local delivery strategy.
Identify any required changes to the accepted product rules before implementation.
This issue covers iOS work associated with GitHub 233.
It does not change the accepted rules by itself.

Acceptance criteria

  • Record supported iOS versions, test device models and application build identifiers.
  • Schedule more than 64 unique requests with the current UserNotifications API through Expo SDK 57.
  • Verify pending request identifiers and delivery beyond the first 64 while the app remains closed.
  • Verify delivery after device restart and record unresolved limitations.
  • Evaluate complete scheduling and replenishment strategies against all accepted rules.
  • Document capacity, permission handling, local storage, cancellation and scheduling failure behaviour.
  • Identify conflicts with closed-app delivery, local calendar progression, notification content and the Day 30 stop boundary.
  • Present concrete product-rule changes if no strategy satisfies the accepted rules.
  • Obtain an explicit product decision before changing those rules.
  • Update the feature specification and ADR 0020 after any accepted rule changes.
  • Implement the selected iOS strategy without silent truncation or server push unless an accepted decision permits these changes.
  • Test setup, permission denial, persistence, sign-out cancellation, scheduling failure and localized reminder delivery.
  • Verify that messages contain the numbered day, slot display names and each serving window.
  • Verify that equal starts produce one combined notification and elapsed starts do not replay.
  • Record device evidence and remaining limitations in repository documentation.

Sources

The legacy capacity limit does not prove current UserNotifications capacity.
Device verification must establish the current behaviour.

No data to display

Actions

Also available in: PDF Atom