Hello ! If creating a .swiftpm in Xcode, are we allowed to simply change Package.swift to target iOS 26.0+? I know a person that did change it (and even won) and had no problems with the playground. I also know that it's technically an autogenerated file and it's ideal to leave it alone. I find it odd that creating a new .swiftpm in Xcode 26.2 right now makes a Package.swift that targets iOS 16.0+, while I created a .swiftpm eleven months ago that automatically targeted iOS 17.5+. – Joe

I managed to come up with my own solution to this without changing the file! :)

Hello! I have also taken a look at the now released submission information. When you choose Xcode 16 (tested in Simulator), I'm assuming that means it will be tested with an iPad Simulator, correct, not Mac Catalyst or iPhone? If you could verify this, that would be great. I'm guessing that iPad is the default based on previous years. Thanks! :)

I apologize, I realize how that question was kind of similar to what I already asked. I guess I am trying to ask, if students do not have any problems with changing the file, will Apple have any problems with changing it, in terms of technicality? It is clear to me that it's not "breaking" any rules for the challenge. Thanks! :)

I appreciate the reply. Is it acceptable to only design an app around a certain orientation (for example, only landscape) and then simply not handle the cases where a user changes to a different orientation? This would completely get rid of the potential risk of changing the file. Of course, in an actual app, this would be a terrible design. However, I am unsure in the context of this challenge and judging. Thanks! :)

Thanks for the help! It must have been something with my particular file that I was trying to load, because I can now open it without a problem. :)