Repository navigation
Log app exit reasons and memory use - #788
Merged
Merged
Conversation
MetricKit exit counts and crash diagnostics are written to the log when iOS delivers them. The app also logs when it is about to terminate, and the background log line includes the memory footprint and the memory left before the limit.
marionbarker
approved these changes
Oct 23, 2026
marionbarker
left a comment
marionbarker
left a comment
Collaborator
There was a problem hiding this comment.
Approve by test. Did a quit, then restart and shared log, see
[14:51:10] [General] App will terminate (memoryFootprint=43 MB, memoryAvailable=2054 MB)
in shared log.
Assuming the rest works as expected.
snickerdoodleparent
pushed a commit
to snickerdoodle-co/LoopFollow
that referenced
this pull request
Nov 4, 2026
Treatment details from a chart pill (loopandlearn#781), CGM sensor states from Nightscout notes (loopandlearn#763), the full predictive low window (loopandlearn#751), app exit reasons and memory use logged (loopandlearn#788), the guardrail alert on the carb and meal edit screens (loopandlearn#786), Loop's automatic boluses as Auto Bolus (loopandlearn#787), Loop IOB and COB on failed loops and the pump battery held (loopandlearn#784); loopandlearn#734 and loopandlearn#771 were in already. Kept from this branch: the time first in the bolus, carb and SMB pills (now "Auto Bolus" for Loop), the weekend profile's own band color and its Treatments entry (moved into Treatment.historyEntries), the override's scheduled end, the alarm title override, and the Live Activity history. The carb double-tap gives way to loopandlearn#781's linked pills, which open any treatment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LgnnHLJbhxmQaEjQNYR5VZ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some users still see LoopFollow die shortly after going to the background with Silent Tune running, and the log can't tell whether iOS killed it for memory, it crashed, or it was swiped away. This logs MetricKit exit counts and crash diagnostics when iOS delivers them (at most once a day), adds a log line in applicationWillTerminate, and adds the memory footprint and remaining memory to the "App moved to background" line.