I submitted an app for review and it was rejected. We've been in discussion with the review team for over a month now, going back and forth providing contracts, legal agreements, proof of security measures, etc. 3 weeks ago the app was rejected again citing the same reason as the initial rejection (lack of proof of partnership agreements), which we have provided proof of. I replied asking the reviewer to scroll back in the history as this issue was already addressed by the previous reviewer. They once again said that we needed to provide it. I replied again with another message containing all of the proof we have submitted to date, responses from legal teams, compliance teams, from partners themselves, etc I also opened an appeal with the apple review board, as this feature is identical to features in dozens of other apps listed in the store. And our partners confirmed everything was above board with what we are doing. After a week of no response I replied to the review asking if its possible to get an update, as the team funding the development of the app are becoming irate with the delays. Its now been 12 days since our last response. Is there any other avenue I can use to try get an update?

Just downloaded and installed the latest Xcode and simulator (Version 14.0 (14A309)). I have an in progress app that listens to keyboardWillShowNotification to move the screen up. As of iOS 16, keyboardWillShowNotification keeps firing every (or every few) key strokes. The additional events seem to all come in with animation duration of 0. Seems like a huge bug, maybe i'm missing something First correct event: keyboard will show: NSConcreteNotification 0x600002d67f20 {name = UIKeyboardWillShowNotification; userInfo = {   UIKeyboardAnimationCurveUserInfoKey = 7;   UIKeyboardAnimationDurationUserInfoKey = "0.25";   UIKeyboardBoundsUserInfoKey = "NSRect: {{0, 0}, {393, 119}}";   UIKeyboardCenterBeginUserInfoKey = "NSPoint: {196.5, 911.5}";   UIKeyboardCenterEndUserInfoKey = "NSPoint: {196.5, 867.5}";   UIKeyboardFrameBeginUserInfoKey = "NSRect: {{0, 852}, {393, 119}}";   UIKeyboardFrameEndUserInfoKey = "NSRect: {{0, 808}, {393, 119}}";   UIKeyboardIsLocalUserInfoKey = 1; }} Second event after typing a few characters: keyboard will show: NSConcreteNotification 0x600002d1c8e0 {name = UIKeyboardWillShowNotification; userInfo = {   UIKeyboardAnimationCurveUserInfoKey = 7;   UIKeyboardAnimationDurationUserInfoKey = 0;   UIKeyboardBoundsUserInfoKey = "NSRect: {{0, 0}, {393, 119}}";   UIKeyboardCenterBeginUserInfoKey = "NSPoint: {196.5, 867.5}";   UIKeyboardCenterEndUserInfoKey = "NSPoint: {196.5, 867.5}";   UIKeyboardFrameBeginUserInfoKey = "NSRect: {{0, 808}, {393, 119}}";   UIKeyboardFrameEndUserInfoKey = "NSRect: {{0, 808}, {393, 119}}";   UIKeyboardIsLocalUserInfoKey = 1; }} Was successfully able to return to previous experience by adding a check if duration exists and is not zero to my callback logic. Feels like that shouldn't be necessary if let keyboardSize = (notification.userInfo?[UIResponder.keyboardFrameEndUserInfoKey] as? NSValue)?.cgRectValue, let duration = (notification.userInfo?[UIResponder.keyboardFrameEndUserInfoKey] as? String), duration != "0" {

I'm working on some apps at the minute, with the intention of running a lot of automated UI tests. Xcode cloud looks great and has a lot of integrated features, but having to make sure I don't run too many hours so my subscription doesn't stop mid dev cycle, or getting a surprise large bill etc, are things I want to avoid. Even the cheapest paid plan for a year works out about the same cost as an M2 mac mini, which would probably be significantly faster than the cloud nodes. Github actions allow you to provide your own machines. But actions requires a lot more scripting, and so far they've been very slow to update Macos/Xcode versions (not sure how this will effect supplying own machine). My preference would be to deploy my own machine for Xcode cloud, similar to what we used to be able to do with Xcode server. I think this is currently impossible right? Is there any word that this might be an added feature in the near future?