I'm also in question of this. We have this announcement:https://developer.apple.com/news/?id=03262020b"Apps for iPhone or iPad must be built with the iOS 13 SDK or later and use an Xcode storyboard to provide the app’s launch screen."Then there is a link to read the guidelines:https://developer.apple.com/app-store/review/guidelines/...which has no mentions of "storyboard". Our company uses no storyboard for our Xamarin app.

Bump. I'd lke an answer before June, please ( calling out you SultanA ).

Thanks for the reply!I understand it's hard to tell, for sure. However, this is the entire content of the reply (cross my heart).-The URLs are both internal developer.apple.com links, so that can't be it.-Not sure about the tone, seems pretty atonal except perhaps the word "ZERO" but that was just emphasis, not snark.-The inline message says it was rejected by a moderator, suggesting even if it was reported by a user, a moderator saw it and agreed, but I still have no idea what the issue could be.As far as the answer goes, Claude31, thanks for your response on that, however, it's still just speculation. If there really is new guidelines for app submission, then those new guilelines should be officially documented somewhere other than a mention in a news post. After all, one can make an app without a storyboard and build everything programmatically, correct?

I've reformatted my original response (changing "ZERO" to "no") and reworking the spacing a bit. I'll see how this attempt goes.

Claude31, Thanks for your guess! When you say "won't even be submitted to review" do you mean it will be outright rejected or do you mean automatic approval? It would seem that if there is a new guideline that requires a storyboard then that new guildeline should be in the official document, correct? If this is a change they expect everyone to make, it seems there should be more mention of it than just a news post.

2023 Update: I was also experiencing the same issue as thomasareed and others on this issue. For me, aapldevusr suggestion of using the AssistiveTouch functionality worked beautifully, but I realized later when looking at the list of files output by the diagnostics that every time I pressed the volume and power buttons and it was showing me the option of turning off the iPad, it was also dropping a diagnostics file into the list (in this iOS iteration, the list is at Privacy > Analytics & Improvements > Analytic Data). So, for others seeing this problem, check the list for updated diagnostic files prior to doing aapldevusr suggestion.