The reason why you can't use the new Observable macro is since the Playground must support iOS 16 as well, and Observable requires iOS 17.

Afaik the app needs to support iOS 16 so the new Observable macro isn't an option unless it's being used as an iOS 17-only feature with an if #available version check or the @available(iOS 17.0, *) attribute.

I'd also like to add that you should test your app playground in Swift Playgrounds as well even if you make it in Xcode, as sometimes some things might not work. Usually that's not the case but it's best to be sure :)

Makes sense now, thanks!

Thanks! I'll file a bug later and post it here. In any case, I realised that even if it were available, this wouldn't work for a Swift Student Challenge app made with Xcode as the Journaling Suggestions API only works on physical devices - on Mac Catalyst / Simulator they are ignored. Perhaps it could've worked for an iPad app with Swift Playgrounds.

Well, perhaps that is the reason then (not the heating, but rather the high CPU usage). What is your app about in broad, vague terms, if you feel comfortable sharing - and what causes it to be this CPU-intense? If you don't want to share your idea I understand. Maybe there are ways to adapt your app for iPads. As I said, you might be able to run it on a Mac only, but I guess also trying to adapt it for iPads would be a fun learning exercise :)

Yeah, I am not sure either - maybe more details will appear in the full terms and conditions. Perhaps you can start a new thread for this and someone from Apple might be able to answer.

You can also use UIKit with SwiftUI code. And SwiftUI should be easy to learn. Good luck!

Glad this helped. For those who get the code signing error I believe you just need to restart Xcode / Swift Playgrounds since you changed the configuration file while Xcode / Playgrounds was running (or do something else to force them read the file again, such as adding a resource file). That’s why maybe it’s best to close Xcode / Playgrounds when editing your Package.swift.

No problem! Glad this helped. Good luck with your submission!

Also, APFS is a file system format 😄

Ignore the “This is analogous to changing the minimum iOS deployment version in an .xcodeproj.” in the second paragraph, I wanted to add this sentence at the end regarding the ”hacky” method.

Is it possible that the tag has been removed from the thread? That would explain why it works now.

Weird, I'm pretty sure I saw that tag when I tried to reply. However, it seems that now I can reply to the thread :)

Now I can reply too :)