I'm seeing the same issue but on iOS (iOS 14 beta 5). Here's the code I'm currently testing with, found it somewhere on the interwebz so I take no credit for it. import SwiftUI struct ShareSheetView: UIViewControllerRepresentable {     typealias Callback = (_ activityType: UIActivity.ActivityType?, _ completed: Bool, _ returnedItems: [Any]?, _ error: Error?) -> Void     let activityItems: [Any]     let applicationActivities: [UIActivity]? = nil     let excludedActivityTypes: [UIActivity.ActivityType]? = nil     let callback: Callback? = nil          func makeUIViewController(context: Context) -> UIActivityViewController {         let controller = UIActivityViewController(             activityItems: activityItems,             applicationActivities: applicationActivities)         controller.excludedActivityTypes = excludedActivityTypes         controller.completionWithItemsHandler = callback         return controller     }     func updateUIViewController(_ uiViewController: UIActivityViewController, context: Context) {         // nothing to do here     } } struct ShareSheetView_Previews: PreviewProvider {     static var previews: some View {         ShareSheetView(activityItems: [URL(string: "https://volante.io")!])     } } * Edit: I just noticed that the ivar activityItems is an array of Any, which let me send a URL wrapped in a Binding<>. This is of course not share:able and this is the reason I was seeing this bug. Maybe this is the same error you've made? To get it working I updated the code to this: ShareSheetView(activityItems: [self.filePath.unsafelyUnwrapped]) I use unsafelyUnwrapped because I know the filePath property will always be set.

Same here. Got a 3 months old MacBook Pro 13" with 4 tb hdd and 32 gig ram that's completely unusable. It's been boot looping 3 days now. Worst part is that Apple can't even set up a service appointment to get it fixed. Talked to them several times on the phone now and every time they try to set it up they receive an error they've never seen before. Got to talk to a senior advisor who reported the bug and he will reach out to me once he hears back. To be honest I'm disappointed on how this is handled. It shouldn't be this difficult to get a computer fixed.

I just managed to fix my laptop. Nothing worked. Tried everything. But now the laptop is working again and I'm actually writing this post from the formerly broken laptop. The solution was to restore the T2 chip. It's fairly easy, but requires you to have another computer with a T2 chip and a USB-C -> USB-C cable. Here's a tutorial on how it's done: 💩://mrmacintosh.com/how-to-restore-bridgeos-on-a-t2-mac-how-to-put-a-mac-into-dfu-mode/ (Replace the chocolate ice cream (or poop, depending on your preference) with http and you'll have a link to a tutorial. Had to do this because I'm not allowed to post links here. 🤷‍♂️)