Recently, I have experienced this issue and the alert keep popping on my playground non-stop although I pressed " allow". I have attached the issue screenshot in this post. Can anyone help me with that.

Hello, I’m encountering an issue where an alert dialog keeps appearing repeatedly in my swift playground project. I pressed "Allow" button but it keeps appearing again. Does anyone can help me about it?

Hello, I am having a recurring issue using Swift Playgrounds version 4.6.4 on macOS 26.1. Upon opening a file and every other time I start typing in the code section I get a prompt, the image below, two or three times. It doesn't matter if I accept or decline all or some of the prompts, as soon as I start typing on another line I get prompted another two or three times for permission. It appears to me that prompt generates every time the preview pane tries to update. Declining the prompt breaks the preview but accepting the prompt only gets you through a single line of code before it appears again. I believe this issue started after I updated to macOS26.1 as I had not encountered it before. I've also opened other files with Swift Playgrounds and encounter the same problem. It could also be unrelated to the update and could be an issue with some permission setting somewhere, however, I have been unable to find what or where it could be. Is anyone else experiencing this? Thank you for your time :)

I’m seeing what looks like a change or possible bug in Xcode when creating a new Swift Playground. When I create a Swift Playground using Xcode (File → New → Playground), the project is generated without an Assets folder. I’ve reproduced this multiple times with fresh Playgrounds to rule out user error and the folder is consistently missing. Previously, new Playgrounds included an Assets catalog by default, which makes this behavior surprising.

Hello, Is it possible to integrate a database into Swift Playground on iPad? Otherwise, what can be done? Thank you.

Several lessons in Keep Going with Apps cannot be completed even when the code is correct. This blocks progression and greys out the Next button permanently.