Swift Playgrounds 4 is available now, from the iPad App Store.

Swift Playgrounds 4 is available now, from the iPad App Store.

First post on the forum, @Maxmudov? If you can be clear about what you are asking, and supply some context, and supporting information, then it will be easier for people to help you.

The Xcode Developer Documentation has a detailed explanations of Apple Archive, including: Decompressing Single Files Decompressing and Extracting an Archived Directory Decompressing and Parsing an Archived String Your example code snippets may have become outdated (or may just be incomplete), but it builds cleanly for me, except for the handling of the "defer" statements. import AppleArchive import System func testDecompressStream(readFileStream: ArchiveByteStream) { guard let decompressStream = ArchiveByteStream.decompressionStream(readingFrom: readFileStream) else { return } defer { try? decompressStream.close() } } Xcode 13.2 (13C90)

This seems to be how the "System Preferences > Input Monitoring" change works. The changes are not instant, but take effect only when the app is quit and relaunched. If the app is running when the change is made in System Preferences, I see a dialog confirming this (with an option to "Quit & Reopen"). I also tried using IOHIDCheckAccess(kIOHIDRequestTypeListenEvent), but this does not give any further information.

Your code does not compile. Try this: struct View1: View { var body: some View { NavigationView { NavigationLink("view2", destination : View2()) } .navigationBarTitle("") .navigationBarHidden(true) } } struct View2: View { var body: some View { VStack{ NavigationLink("view3", destination : View3()) } .navigationBarTitle("") .navigationBarHidden(true) } } struct View3: View { var body: some View { Text("Hey") .navigationBarTitle("") .navigationBarHidden(true) } }

Hi @BDCConfused... first post on the forum? Try posting your code in a code block (using "Paste and Match Style"), rather than a photo or screenshot. Then it will be easier for people to help you. Why do you think your issues are related to Dark Mode?

When uploading in the background, the temporary file should be deleted (on the main thread) in the upload task's completion handler. That is, the upload task must have finished (with success or failure) before you delete the temporary file. In URLSessionTaskDelegate, that would be in: urlSession(_:task:didCompleteWithError:) (Of course, if there was an error, you might want to try again.)

Depending on your Mac, you probably have much more than 100% available. It's a bit like footballers who always give 110%. On an 8-core processor, you would have 1600% available. So 100% may not be as much as it seems. I want my Mac to work hard, so I was pleased to see it achieve 1200% yesterday.😀

I think you would have to use two UNNotifications for this case. The first notification (start of next month, non-repeating) fires when you want the repeating notifications to start. Your handler for this notification starts the second notification (daily, repeating).

It is very unlikely that Apple will do this. However, they have provided a mechanism for you to do it yourself... You can create the same effect, by making your own ringtones and message tones. When you record the tones, you could adjust their volume levels, to suit. You can even have per-sender message tones (with different volumes), to distinguish between more and less important senders. I use the Fission app to produce my tones... many such apps are available.

Have you considered using a convenience initializer?

Did that work for you, @airbolt?

there is no storyboard or xib involved So why are you declaring it like this? private var userLocationButton: CLLocationButton! Rather than (say): private let userLocationButton = CLLocationButton() ...and then set up userLocationButton, rather than bothering with a separate "let button = CLLocationButton()" Alternatively... I tried setting up a new project with your Code above and everything just works fine So just use that code?

There is a serious issue with the latest App Store version of Xcode 13.2. See this thread:   https://developer.apple.com/forums/thread/696504 If you want to try a fixed 13.2... The workaround is to download an updated Xcode 13.2 from Apple Developer (Applications): https://developer.apple.com/download/release/