Repository navigation
Swift Logger property is not concurrency-safe because it is nonisolated global shared mutable state #181683
Description
I tried turning on Swift 6 concurrency features for fun, and it found:
Logger.swift:42:22: warning: static property 'shared' is not concurrency-safe because it is nonisolated global shared mutable state; this is an error in the Swift 6 language mode
40 | /// ```
41 | @objc(FlutterLogger) public final class Logger: NSObject {
42 | private static var shared = Logger()
| |- warning: static property 'shared' is not concurrency-safe because it is nonisolated global shared mutable state; this is an error in the Swift 6 language mode
| |- note: convert 'shared' to a 'let' constant to make 'Sendable' shared state immutable
| |- note: annotate 'shared' with '@MainActor' if property should only be accessed from the main actor
| `- note: disable concurrency-safety checks if accesses are protected by an external synchronization mechanism
43 | private let outputWriter: OutputWriter
44 | public let logLevel: LogLevel
Activity
[-]Logger property is not concurrency-safe because it is nonisolated global shared mutable state[/-][+]Swift Logger property is not concurrency-safe because it is nonisolated global shared mutable state[/+]flutter-triage-bot commentedon Jan 29, 2026
Issue is assigned to multiple teams (infra, ios). Please ensure the issue has only one
team-*label at a time. Usefyi-*labels to have another team look at the issue without reassigning it.flutter-triage-bot commentedon Jan 29, 2026
The
triaged-ioslabel is irrelevant if there is noteam-ioslabel orfyi-ioslabel.flutter-triage-bot commentedon Sep 21, 2026
This issue is assigned to @cbracken but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
cbracken commentedon Sep 30, 2026
As luck would have it, I actually started on this one a while back (when I tried once more for
os_log) but never finished! Thanks for the reminder.cbracken commentedon Sep 30, 2026
Actually as luck would have it, I actually did land it in #181683
github-actions commentedon Oct 14, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.