Background task files that are symlinks or unreadable are quarantined or skipped instead of trusted.
What's wrong with this entry?
The background task roster file and the dispatch files it works with are now inspected before use. Symlinks and anything that is not a regular file are quarantined or removed instead of read, and a file that cannot be inspected produces a clear skip message rather than being treated as missing.
- Message on skip:
bg roster.json update skipped: the file could not be inspected - Read errors that mean the filesystem refused (ENXIO, EFBIG, ELOOP, ENAMETOOLONG) take their own path rather than being lumped in with "not found"
bg roster.json update skipped: the file could not be inspected
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task