Make sure to file a feedback for this and link it here. I think it's good that this pop-up after restart exists, since one could forget that they gave access to a remote desktop app. Maybe a setting to prevent these kind of appearing again after restart / give you an option to select for how much time you'd like to give access (such as an hour / a day / a week / indefinitely etc.) would be helpful.

Maybe this will be a program just like the SRD? [quote='756836021, flexorium, /thread/756836, /profile/flexorium'] Who at Apple should I keep in touch with and what is the best way to communite with that team. [/quote] If you want to keep in touch with the Product Security team, their email address is product-security@apple.com, and they also have a PGP key (since you can send vulnerability reports which are sensitive in nature). They'll definitely make more announcements on this in the future, so keep an eye on the security research website.

I had a similar issue on Monday when I tried to create a post with the Apple Intelligence label. Anything posted with this tag resulted in a sensitive content warning. To answer your question in the gist, I believe Apple Intelligence features will be available in a later beta.

[quote='756823021, jvigneshcs, /thread/756823, /profile/jvigneshcs'] var value: Value { lock.read { _value } } [/quote] Isn't SynchronizedBarrier<Value>.value a read-only computed property (i.e. doesn't have a setter), and thus you can't set _timedEvents.value to a new value using _timedEvents.value { $0 = newValue }? I'd try changing SynchronizedBarrier<Value>.value to this: var value: Value { get { lock.read { _value } } set { lock.write { _value = newValue } } } I haven't tested it, so let me know if this works or not.

[quote='756823021, jvigneshcs, /thread/756823, /profile/jvigneshcs'] _timedEvents.value { $0 = newValue } [/quote] I'm curious, is there a reason why _timedEvents.value = newValue doesn't work? Never mind, I think I understand now. Looking at the crash report and at the Swift runtime, it seems that something results in a dangling reference, since it calls fatalError with this description: swift::fatalError(0, "Object %p of class %s deallocated with non-zero retain " "count %zd. This object's deinit, or something called " "from it, may have created a strong reference to self " "which outlived deinit, resulting in a dangling " "reference.\n", object, descriptor ? descriptor->Name.get() : "<unknown>", retainCount); I think the way you're using nested computed properties somehow results in a dangling reference. Perhaps the object causing this is newValue, though I'm not sure. Maybe you could reproduce the issue and record the logs with the Console app on Mac to see if you find any other clues?

Maybe you could record system log messages and filter the irrelevant ones with the Console app to find out more about the error behind this? As a workaround, you can install Xcode 16 on the host and send your binaries / app to your VM (you could use File Sharing), though setting up remote debugging will require additional steps.

I got the same dialogue and error (using the Restore Image from the downloads website). Perhaps you need a macOS 15 host as well.

I'm curious, why don't you book a WWDC lab for that question and other related ones you may have? Perhaps "App Store business and marketing consultation" is the lab you're looking for.

Of course, the new UI should be preferred when users are supposed to create their images with prompts. I'm asking if I could use the generative image model behind this feature for my app to automatically generate a few images based on the context / image suggestions. Also, apparently, creating a new post with the Apple Intelligence label results in a sensitive content error and won't allow posting it.

I think it would be better to post your app's crash report, though you included most of its information in your post already. Running an INSERT or DELETE with the exec() method does not result in an exception; we just get an error saying that the table in the command does not exist. This makes me think there's an error accessing the database file, though I am not sure. exec() crashes when it gets to sqlite3VdbeMemGrow in the sqlite3VdbeMemStringify call. It seems like a memory allocation-related segfault bug in SQLite (somewhere here, to be precise: https://github.com/sqlite/sqlite/blob/master/src/vdbemem.c#L242), so I'm not sure what Xcode changes could determine this.

I filed a feedback, FB13660312, as I ran again into this issue when creating my Swift Student Challenge project - this time in a different scenario, but the issue is the same. I'd say it follows the same simplified example as before, except the value was used differently inside the sheet (it was passed to an UIViewRepresentable which used it - no if statements were directly used inside the sheet's trailing closure). I'm curios to hear what others think, do you think this is a valid race condition bug?

You should’ve received an email immediately. You can also check if your application was received by going to https://developer.apple.com/swift-student-challenge/apply/ (make sure you’re logged in). The website says “We’ve received your application” if it was sent properly. You should contact swiftstudentchallenge@apple.com for help, especially if the website indicates that an application was not received.

I know the deadline just passed, but I hope you’ll find this helpful. Good luck with your submission! The camera features (not taking AR into consideration), as you already know, do not work in the simulator app, but if you choose the My Mac (Mac Catalyst) run destination in Xcode, they should work fine. It should also work fine in Swift Playgrounds. However, since you made an AR app, I think the best option would’ve been Swift Playgrounds on iPad, as some AR features don’t work on Mac. It depends on what AR features are used by your app. As for the test device, I am not sure - I believe the app should work without any extra device.

@Claude31 Yes, I tried that. I also thought it could be the $0 but it still doesn't work :( I do have a workaround that I might implement (moving the text in the parent class), but I'm also wondering what could be the problem here. Could it be related to Item.myarray's type (an array of structs that conform to Codable)?

I don't think it's a good idea, as the rules specify iPadOS 16 or later. I think your app must work on iPadOS 16 as well. Check this thread. Perhaps you could add extra features to iPadOS 17 devices using the other solutions presented in the thread you mentioned. I sent the response on the thread you mentioned before the full terms & conditions were published.