Posts

Post not yet marked as solved
3 Replies
I found this when I opened my info.plist file: <key>UISupportedInterfaceOrientations</key> <array> <string>UIInterfaceOrientationPortrait</string> </array> <key>UISupportedInterfaceOrientations~ipad</key> <array> <string>UIInterfaceOrientationPortrait</string> <string>UIInterfaceOrientationPortraitUpsideDown</string> <string>UIInterfaceOrientationLandscapeLeft</string> <string>UIInterfaceOrientationLandscapeRight</string> </array>Is this some new thing where Xcode is forcing iPad apps to have all orientations or am I misunderstanding the UI? I don't see a way in the project settings to specify iPad orientations separately. I was able to solve my problem by editing this file manually.
Post marked as solved
5 Replies
I personally tried to put off working with Swift as long as I could, but many things pressured me into using it early, including market forces (non-technical customers specifically asking for their apps to be written in Swift, knowing only Apple's marketing information) plus having to work on apps that had been started in Swift by other developers. I am glad it is somewhat stable now, but I'm still disappointed in how quickly Apple has moved away from supporting "old" versions of Swift. This week I had occasion to do some maintenance on an app I wrote less than three years ago, and when I opened it, I was told that not only was Swift 3 out of date, but it could no longer even be converted to Swift 5 by Xcode.As for the sting situation, the solution is pretty easy: have an index that is lazily initialized, so it doesn't take up space unless we need it.Frank
Post marked as solved
5 Replies
Thanks for the notes, and the link.If nothing else, I'm disappointed about the fact that Apple saw fit to release something as a finished product but then make major breaking changes to it every year for four years in a row.I worked as a C and C++ developer for more than 20 years, and never in that time (or since, as far as I know) has anyone changed the languages in a way that breaks older code. Yes there's something to be said for making improvements even at the expense of compatibility, but I'm not really sure what the point was of rushing an unfinished product out the door instead of waiting a couple of years to get it right. It's not as though we didn't have a way to write apps before 2014.Alloc init,Frank
Post not yet marked as solved
3 Replies
Thanks, I know how to do that... what I was wondering is whether I could share all the files at once without having to do this individually.
Post not yet marked as solved
3 Replies
Thanks, I did have a scene delegate, and removing it fixed the issue.I guess a scene delegate is something new that Xcode gives you by default. I had never even heard of a Scene before.