Is this review waiting time currently normal, I think all of us must acknowledge the situation and brace for it, by anticipating submission before the app publication planned date. Reviews taking a few days are now usual. Pounding on reviewers to ask for expedited review appears useless, as well as posting messages here. It just clutters the forum with posts on which no developer can do anything (except lament with the OP) and where App Review is always the same formatted answer. @abdev19, waiting from Wednesday morning till Friday is not a huge delay. Wish you to get rapidly your app reviewed. When so, don't forget to close the thread.

It is not the first time iOS has problems with accented words. I had a problem with UIActivityViewController failing to Airdrop if filename has an accented char. FB22253128

It looks like there is a systemic problem here. Appstore review process is no more able to cope with the huge flow of submissions (even submitted by robots ?). I would not be surprised to see significant changes in the submission process in the near future in order to regulate this flow. Not sure billing for submission would be a good option (even with a number of free submissions ), but they have to find something.

Welcome to the forum. Is it what you get immediately after accessing appstoreConnect ? https://appstoreconnect.apple.com/apps or https://appstoreconnect.apple.com What happens when you open the pull down menu on the right "Piotrs Pavlovs" ?

Welcome to the forum. Your app is dealing with healthcare. Read carefully the guidelines, 1.4 and 1.4.5 in particular. Are you asking to test for debug or for experimenting the app ? If the latter, take care that by solliciting experimenting your app outside of those guidelines (and worse, without going through review) you could even risk account termination.

You seem to be unlucky. You have posted tens of posts for this exact same issue. But you never closed any thread to indicate when finally the review was completed. You should've.

As you can charge with Magsafe, you're safe. In such a case, I would not pay $200 for a repair that will probably not solve anything. Did the problem occur just after installing 27.3ß ? If so, you could: return to a stable iOS wait for the next release of iOS Then you'll see if it's a hardware issue. Of course, you should file a bug report.

@Deniz, welcome to the forum.   is review running 7 days a week Yes. I have submitted (revisions) several times these last months and got validation even on Sunday.   For an app that requires sign-in, is it common for review to take a little longer since the reviewer has to log in and test? Likely. if you browse the forum, you'll notice that some (many?) developers are reporting first time submission to take longer than in the past (due to the number of AI generated apps ?). So it is not totally specific to your app. But it should take a only few days before you get accepted or receive feedback.

Pretty sure this will be the last SwiftUI app I'll ever write. Never say never… 😉 Why didn't you start directly with Appkit of UIKit ? I personally have mixed feelings about SwiftUI, because, for the sake of apparent simplicity, it forces sometimes into convoluted solutions. IMHO, SwiftUI is great for rapid prototyping, but I do not use it for complex apps.

I've searched extensively but could not find how to. So I use a workaround: I test gender for each supported language (out of app) and use this information to adapt to the app selected language. But not sure that will be robust over time.

Bem-vindo ao fórum. Não é necessário abrir vários tickets junto do suporte técnico. Isso não vai acelerar o processo. É possível que, devido ao 4 de julho, os pedidos se tenham acumulado um pouco. Enquanto espera (logicamente, não deverá demorar muito) para poder submeter as suas aplicações, pode utilizar o Xcode e continuar a desenvolver.

Problème comes from, not from command. @State public var contentView = ContentView() I have tested this very simple code to show: struct ContentView: View { public func importTerms() { print("\(showFileImporter)") showFileImporter = true print("\(showFileImporter)") } var body: some View { Button("Test") { importTerms() } } } struct ContentView2: View { @State private var content = ContentView() var body: some View { Button("Test2") { content.importTerms() } } } If I call ContentView(), and tap "Test", I get the correct result. false true But If I call ContentView2(), and tap "Test2", I get the wrong result, var is not changed. false false My guess is that with this declaration of state var ContentView, you create 2 instances, and there is a confusion in the showFileImporter state var at system level. you update var for instance2 which is ignored by the system which uses instance1 (in print). Someone more expert in SwiftUI may provide more accurate explanation. You could use environment variables for showFileImporter and remove the contentView state var to solve the issue. Note: in Swift, you don't need to end statements with semicolon.

Problème does not show on iOS 26.2 simulator. So looks like it was a temporary bug that has been rapidly corrected…

Jumping into the discussion, I have performed about 10 submissions in the last 2 weeks. They all went expeditely, with approval in less than 24 hours. Pretty good, isn't it ? @Etresoft, This is a developer support forum. … it's become a venue for complaining about App Review. unfortunately, I agree with you. The forum is turning to a useless kind of Wailing Wall.   The rumours are that it's the same inside Apple due to AI slop Will we see the day where reviews are billed, as a way to limit the flow of AI app submissions.

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.