Skip to content

Let a nav-data download survive leaving the app - #40

Merged
RISCfuture merged 1 commit into
navdata/atomic-installfrom
navdata/continued-processing
Sep 9, 2026
Merged

Let a nav-data download survive leaving the app#40
RISCfuture merged 1 commit into
navdata/atomic-installfrom
navdata/continued-processing

Conversation

@RISCfuture

@RISCfuture RISCfuture commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

The consent screen asked the pilot to leave the app open until the import
finished, because a plain Task gets seconds of runtime once the app is
backgrounded and the transfer would restart from nothing next launch. A
BGContinuedProcessingTask buys that time, and gives the system a progress
and cancel affordance the app does not have to draw.

This was blocked, and is not any more. The system expires these tasks as
conditions change, and cancels them outright when the app is swiped out
of the switcher, without telling the app. Against an import that emptied
the live dataset before writing its replacement, that meant an empty
airport database — the state the app cannot work from. An import now
writes a generation nothing is reading, so a cancelled one costs a file
that the next launch reclaims.

The task is an enhancement, not a dependency: if the system will not
start one, the import runs exactly as it did before. The request asks to
start now or not at all rather than queue, because an import would rather
run unprotected than wait to begin.

The identifier is a wildcard prefix, which is how continued-processing
requests are permitted — the prefix is registered and each submission
names itself beneath it. No UIBackgroundModes entry is involved; that
belongs to app refresh, and the comment claiming otherwise was describing
BGProcessingTask, a different API for unattended work that is still its
own piece of work.

Progress is reported because it is required, not merely useful: a task
the system reads as stalled is expired to reclaim its resources.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01471376Uhug2TYZN8RDFGtq


Stack created with GitHub Stacks CLIGive Feedback 💬

🤖 Generated with Claude Code

https://claude.ai/code/session_01471376Uhug2TYZN8RDFGtq

@RISCfuture
RISCfuture force-pushed the navdata/continued-processing branch from 88212f8 to 07da8df Compare September 8, 2026 07:17
@RISCfuture
RISCfuture force-pushed the navdata/continued-processing branch 2 times, most recently from 4c14f0a to f71ad51 Compare September 8, 2026 08:02
@RISCfuture
RISCfuture force-pushed the navdata/continued-processing branch from f71ad51 to ee87aeb Compare September 8, 2026 08:03
@RISCfuture
RISCfuture force-pushed the navdata/continued-processing branch 2 times, most recently from 3aba65d to b8211f3 Compare September 8, 2026 16:13
@RISCfuture
RISCfuture force-pushed the navdata/continued-processing branch from b8211f3 to bbb4fb6 Compare September 8, 2026 16:19
@RISCfuture
RISCfuture force-pushed the navdata/continued-processing branch from bbb4fb6 to ea5da2c Compare September 8, 2026 16:26
@RISCfuture
RISCfuture force-pushed the navdata/continued-processing branch from ea5da2c to 68caa82 Compare September 8, 2026 16:33
@RISCfuture
RISCfuture force-pushed the navdata/continued-processing branch 2 times, most recently from 29d6f32 to f8e38bb Compare September 8, 2026 17:10
@RISCfuture
RISCfuture force-pushed the navdata/continued-processing branch from f8e38bb to 3dbc098 Compare September 8, 2026 18:09
The consent screen asked the pilot to leave the app open until the import
finished, because a plain Task gets seconds of runtime once the app is
backgrounded and the transfer would restart from nothing next launch. A
BGContinuedProcessingTask buys that time, and gives the system a progress
and cancel affordance the app does not have to draw.

This was blocked, and is not any more. The system expires these tasks as
conditions change, and cancels them outright when the app is swiped out
of the switcher, without telling the app. Against an import that emptied
the live dataset before writing its replacement, that meant an empty
airport database — the state the app cannot work from. An import now
writes a generation nothing is reading, so a cancelled one costs a file
that the next launch reclaims.

The task is an enhancement, not a dependency: if the system will not
start one, the import runs exactly as it did before. The request asks to
start now or not at all rather than queue, because an import would rather
run unprotected than wait to begin.

One fixed identifier is registered and submitted, advertised verbatim in
BGTaskSchedulerPermittedIdentifiers. A wildcard entry there permits the
concrete identifiers beneath it, but the wildcard itself is not one the
scheduler will register a handler for; since a handler has to be
registered while launching, the identifier it answers for has to be known
by then, and naming each submission after its own import is not open to
us. No UIBackgroundModes entry is involved; that belongs to app refresh,
and the comment claiming otherwise was describing BGProcessingTask, a
different API for unattended work that is still its own piece of work.

Progress is reported because it is required, not merely useful: a task
the system reads as stalled is expired to reclaim its resources.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01471376Uhug2TYZN8RDFGtq
@RISCfuture
RISCfuture force-pushed the navdata/continued-processing branch from 3dbc098 to 00084af Compare September 9, 2026 06:39
@RISCfuture
RISCfuture merged commit cce1740 into main Sep 9, 2026
5 checks passed
@RISCfuture
RISCfuture deleted the navdata/continued-processing branch September 9, 2026 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant