Is it possible to use the Multipeer Connectivity framework for a messaging service? For example a user provides permission for the application to occasionally run in the background like other apps so that the application can forward messages and data to the intended recipients. I am under the impression this is how the Find My network behaves so I was curious if similar functionality could be achieved with this framework. Or is the Multipeer Connectivity framework solely for user-centric activities where sessions must be started and maintained with foreground app usage.

While working through a SwiftUI Tutorial, I found that using: FileManager.default.url(for:, in:, appropriateFor:, create:) to locate a directory for persisting some data, does not work on Apple Silicon Macs when building an app for the "My Mac (Designed for iPad)". Quitting the app loses all state saved. Both the iPhone and iPad test devices are able to save and restore state using this method as usual. Is this the expected behavior? I expected that the M1 platform would be capable of simulating a similar file system for the application. Targeting macOS, iOS, and iPadOS, what's the simplest method to acquire a valid "Documents" or "Data" directory to persist information across launches and after app updates? (Before going nuclear with CoreData, just hasn't been the most friendly API to work with in my experience so far)

Basically every time I open the preferences window and then click on one of the tabs (accounts, behaviors, etc...) Xcode crashes. Running macOS 11.0.1. This occurs in Xcode and Xcode-Beta. Did not find any similar posts mentioning this issue but I thought I'd ask in case there was anyone else running into this. Problem Report for Xcode - https://developer.apple.com/forums/content/attachment/95d40578-d2d0-4713-ac5a-4969f614ef66 Problem Report for Xcode-Beta - https://developer.apple.com/forums/content/attachment/0ee3c3a3-b34b-4e19-a88b-c46caf9a3b35