extensions-widgets

Widget crashes and memory issues stem from improper timeline management and lifecycle handling. Enforce strict timeline policies, respect the ~30MB sandbox constraint, and use prefetch in the main app with TimelineProvider reads to safely fetch data. This prevents stale data and unresponsive widgets across Home Screen, Lock Screen, StandBy, and Control Center widgets.

App Groups enable safe data sharing between your app and extensions in separate bundle containers. Store prefetched data via the main app, then read it through TimelineProvider in widgets and Live Activities. This pattern prevents data sharing failures and ensures widgets access fresh, validated information.

Live Activities and Control Center controls require proper lifecycle handling tied to timeline updates. Apply the same timeline discipline, data sharing via App Groups, and extension lifecycle patterns used for widgets. This ensures responsive controls, correct data updates, and prevents crashes in dynamic system experiences.

Stale data and unresponsive widgets result from improper timeline refresh cycles or missing gallery presence configuration. Use correct timeline patterns with App Groups-based data sharing and ensure the main app prefetches data that TimelineProvider reads. Validate that your widget's timeline policy complies with platform requirements.

Yes. All widget types—Home Screen, Lock Screen, StandBy, Control Center—and Live Activities use the same App Groups data-sharing architecture. Enforce consistent timeline management and extension lifecycle patterns across all extensions to avoid crashes and memory issues in any context.

Extensions operate within a ~30MB memory sandbox. Design your timeline refresh strategy, data payload size, and prefetch logic to respect this limit. Avoid storing large datasets in App Groups; instead, prefetch and cache only essential data in the main app for TimelineProvider reads.