But I wonder why they don't just ask instead of jumping to a conclusion? They often reject the app for simple reasons these days. And they are often wrong. They have no time to do it. And it looks like the reviewer puts himself in a basic user shoes.He will not read any user manual but checks if the UI is straightforward. Visibly he did not feel so. So he may not be wrong but just a bit exacting. Remember also that if a user gets confused for 10 seconds with an app, he will just discard it. So it is your best interest to make it as easy to understand as possible. For this, IMHO, @darkpaw, is right.

When I receive similar message, it is immediately followed by another one stating that Your app, XXXXXXX, is "Ready for Distribution". Did you receive it ?

I asked a related question a few years ago and got a valuable answer from Quinn. Discouraging to use Fuse. If that may help. https://developer.apple.com/forums/thread/768957 I profit of this thread for a wider comment. There are several cases of apps or devices that ran on MacOS 7 or 8 which were really valuable but are progressively getting lost. That's the case of HFS disks content, but also for apps like Hypercard. Would be really great to be able to revive them "as is" on MacOS 26.

Thanks for taking the time to reply. Unfortunately, that seems to apply only not "normal" characters.

As of June 28, I searched on the appstore (in France) and think I found it (developer: Lucian-Stefan Lacatus) If so, please don't forget to close the thread by marking the correct answer. I noticed something a bit surprising: app language is indicated as English only, but all the information about the app are in Romanian.

deleted -- too old OP.

IB is such a perfect tool to visually build a layout, I am very sad to see it so neglected. Fully agree. Doing in code makes is so hard to understand and quasi impossible to maintain. And I don't find SwiftUI so good to design precise UI (where many items need to be precisely positioned). I compared Xcode 26.3 and 16.4 : 26.3 takes between 9 and 12s to open the first view in IB, instead of 6s. Would be really interesting to know what it does differently.

Even though one may understand your frustration, you should blame yourself for the delay. Several of your submissions were rejected because app crashed. If you read the guidelines, it is explicitly reminded that review is not to be used as a debugging help. So it appears that the real delay is 1 day, since June 23: Resubmitted again with additional bug fixes. Note that after first acceptance, there is an expedited process for Bug Fix Submissions: For apps that are already on the App Store or alternative distribution, bug fixes will not be delayed over guideline violations except for those related to legal or safety issues. If your app has been rejected, and qualifies for this process, please use App Store Connect to communicate directly with the App Review team indicating that you would like to take advantage of this process and plan to address the issue in your next submission. I wish you make 10 000$ in 3 weeks once your app is accepted. Have a good day.

Should I:  Create a completely new App ID and submit as a new app? I do recommend NOT to do so. That would create more confusion, with a risk of being flagged as spam… Or worse, considered as "manipulative or misleading behavior or other fraudulent conduct will lead to your removal from the Apple Developer Program" Impossible to speak for the reviewer, but some thoughts, hoping it will help. What type of an app is ? Is it a paying app ? Does it include purchase or subscription ? Have you checked your app on various simulators (different sizes, iPhone, iPad, Portrait and landscape) ? Could you go to test flight ? Or at least test your app with a few other people. Their genuine comment may help you understand the issue. After this, you could either appeal the review or resubmit, explaining what you have done since rejection in the comments to reviewer. Take care to use soft wording, not complaining or criticising the review process in those comments, but just be very factual.

is it customisable with third party apps ? I don't think so, this is a system function. What type of customisation would you need ? You could file a Feedback asking for improvement and capability to change some settings.

There is a much better solution to prevent scams: Get Your iPhone to Ask Callers Who They Are Before You Answer https://www.macrumors.com/how-to/get-iphone-ask-callers-before-answer/ And this is compliant with any country regulation.

I may be wrong, but AFAIK, Recent is limited to 5 items (FIFO mode). So may be Xcode team has considered rightfully that the Clear recent was not very useful and just cluttered the menu when Recent list never gets cluttered.   This is important as with time it might be cluttered with unused destinations. Have you an example with a longer list in Recent ?

What iPad have you got ? You could generate screenshots on this iPad, then, using Preview app, open the screenshot and resize it to 2064 x 2752 pixels (portrait) or 2752 x 2064 pixels(landscape)

Don't know if that would change anything, but did you try to disable Apple Intelligence in Xcode ? May be Xcode tries to build something from the storyboard ? https://www.reddit.com/r/Xcode/comments/1h76ng9/disable_xcodes_apple_intelligence_feature/ or https://developer.apple.com/documentation/Xcode/setting-up-coding-intelligence

You may use .onKeyPress: struct ContentView: View { @State private var vText: String = "" var body: some View { HStack { TextField("Enter text", text: Binding( get: { vText }, set: { newValue in vText = newValue } )) .onChange(of: vText) { oldText, newText in let typed = newText.replacingOccurrences(of: oldText, with: "") if newText.count < oldText.count { print("backspace") } else { print("typed char is: ", typed) } } } .onKeyPress(characters: .controlCharacters, action: { keyPress in if vText.count == 0 { print("Control key \(keyPress.characters)") // Do whatever needed and test if backspace } return .ignored // handled would intercept the typing }) } } Let us know if that works (don't forget to close the thread if so).