This feels like a very awkward change. I'm not sure what the appropriate resolution for this is, but I guess we could assume it's isolated? .onPreferenceChange(MyPreference.self) { value in MainActor.assumeIsolated { myValue = value } } Of course this will crash at runtime if that assumption is incorrect. This feels particularly bizarre now that all View conformances are automatically @MainActor now.

When Xcode launches a process it will unredact the logging for that single process if it is for an application that you are privileged to view. (One that is able to be attached with a debugger) Oh! So because I’m running the debug build of the app, from Xcode, I’m able to see unredacted logs, just like I would in the console, even though I’m exporting them. Testing this exact same code with a TestFlight build confirms the private data is correctly redacted, so this absolutely solves my problem. Thank you so much!

Has there been any movement with this? I've just encountered this bug while increasing my deployment target from iOS 11 to iOS 12. I also use SSDP in order to search for UPnP devices on the network.