User Profile

At the moment, I seem unable to modify my Xcode cloud project settings -- this is something that has worked fine for me in the past. Each time I modify something (e.g. Xcode version, description, etc) and click 'save', I see a loading spinner, and then I'm kicked back to the App Store Connect home page. Returning to Xcode Cloud shows that no settings were updated. Is this happening for others? (Or has anyone run into a similar issue before).

It seems that iOS 15 has broken modal view controller 'drag to dismiss' under the following configuration: The presented modal contains a nested scroll view && the outer scroll view is horizontally scrollable In iOS 13 and 14, UIScrollViews would propagate scroll events correctly, and despite the nested scroll view complexity, downwards scroll events would bubble up to the modal drag-to-dismiss gesture when appropriate. In iOS 15, this seems to have broken (even for builds still targeting iOS 14). I'm presuming some of the internal logic for modal drag down changed to support the new sheet presentation APIs, and in doing so, nested scroll view support broke. I'm curious as to how many others are running into this issue, and if anyone has found a workaround. I've submitted a bug report, although given how late it is in the beta cycle I'm not hopeful we'll see a fix before the public release of iOS 15.0.

I recently updated a macOS catalyst app, using the latest version of Xcode 11. Today, I started hearing reports from users that downloading the app presents an error message: The current version requires OS X 12.0 or later, but you can download the last compatible version. This is concerning - anyone trying to download the app is now deterred by an error message. I'm unsure whether I've altered something, or whether it's a problem on the Apple side. It seems 100% reproducible (you can search for 'Class Timetable' on the macOS App Store to see the error message). Of note, if you browse the App Store listing - compatibility is listed as 'macOS 10.15 or later'. My guess is that the incorrect minimum version is getting used here: the iOS variant of the app does have a minimum version of iOS 12.0, but the Mac App Store seems to be reading this and not the correct macOS minimum version number. Has anyone else run into this - any suggestions of what it might be/how to get this resolved? I've reached out to Apple but haven't had a full answer yet.