Hi Richard, thanks. I did already set request.revision request.revision = VNRecognizeTextRequestRevision3 Could you find the project in FB ?

I may have found a cause (may be not all causes). Somewhere I had set : request.recognitionLevel = .fast to retry recognition. I eliminated this, seems to work somewhat better. I have built a minimal project ; how can I send you ?

Hi Richard, thanks for returning. Environment : Xcode 26.3 MacOS 15.7.9 (24G830 Tested on simulators (iOS 26.1, and many other version of iOS ) Tested on iPad 15.8.8 and iPhone XS 18.7.9 In fact, I notice recognition of single letters (like I) is whimsical ; it may or may not work. I did filed a pretty similar FB a few years ago: Jun 7, 2022 – FB10066541 I will try to make a minimal project. In the meantime, if there is a mail to which I can send the reference of the (free) app on the appstore just to see what happens.

if you Can load build into TestFlight, that's OK… 😉 Could you show the Signing & Capabilities page (blur partially some parts of course.

Yes, of course. What is the problem ? struct ContentView: View { var body: some View { Button("hi") { print("Hello, World!") } .frame(width: 500, height: 300) .background(Color.blue) .foregroundStyle(Color.white) .font(.system(size: 60)) .bold() } } Don't forget to close the thread by marking the answer as correct if that's OK. Otherwise, please explain the issue.

I doubt that Apple's review team checks what exists on Google Play.   Written by kamran_Akram “The app’s description, name, and icons includes references to Pet Shop Owner Simulator 3D.” However, app may be rejected if it has visual elements specific to Android (e.g., Android's style buttons).   Written by kamran_Akram if there is something specific in my App Store metadata that I should change. Most likely, yes. Why do you mention simulator 3D in the iOS version as it is not the name of the app ?

Could you explain the context, show the code, show AI fix, tell which AI… Without such information the post is without any interest. A very good post from Quinn to look at: https://developer.apple.com/forums/thread/706527

We may understand your frustration for the long delay. Hope you get a resolution soon. What type of an app is it ? Please note that it is useless to repeat many times the same post about review delays. Developers here can do nothing about it, so it is just cluttering the forum.

I've finally solved by building directly the accessoryView, by creating UIButtons (and no more buttomItems) and using config. Here a code extract for those interested: let letterBack = UIImage(named: "letterBackground")! if #available(iOS 26.0, *) { let targetSize = CGSize(width: 40, height: 40) let scaledImage = letterBack.scalePreservingAspectRatio(targetSize: targetSize) var config = UIButton.Configuration.filled() config.background.image = scaledImage config.background.imageContentMode = .scaleAspectFill let bar = UIView(frame:CGRect(x: 0, y: 0, width: 200, height: 44)) ?? create bar as UIView and not UIToolbar config.baseForegroundColor = .black config.titleAlignment = .center // set each button config.title = "I" let letterI = UIButton(configuration: config) letterI.frame = CGRect(x: 5, y: 0, width: 40, height: 36) letterI.addTarget(self, action: #selector(letterButtonTapped(_:)), for: .touchUpInside) letterI.tag = 1. // Use the tag to know which button was tapped bar.addSubview(letterI) // the same for other buttons // set the UIView as the accessory answerTextField.inputAccessoryView = bar }

Thanks to @Benzy Neez in S.O, I could suppress the round background. https://stackoverflow.com/questions/79995564/solving-liquid-glass-problems-in-uitoolbar But that did not change the spacing which remains too large. I have tried to use fixedSpace(_ width: CGFloat) to no avail.

@Ankooo in addition to what @Tomato said… Hope you resolved the issue. If so, it would be good behaviour to feedback and close the thread. Otherwise   The notice stated that our account had repeatedly submitted apps with unresolved guideline violations How many rejections ? what causes ?   We want to resolve this properly and rebuild trust. We would be grateful for any guidance from Apple Team Don't expect guidance from review team, they check and notify but are not a support team to resolve issues. As for trust, t unfortunately seems too late. When next reviewer checks your app and notice the list of rejections, just to find yet another rejection, they may logically think you try as many times as possible since it succeeds by chance. And they may consider they are too busy, with so many other apps waiting for review, to continue to play this game. How is it you could not fix the problems ahead of submission ? Did you read thoroughly the guidelines, the developer agreement…

@Fares, if that can be implemented, that's a good idea. You should submit as suggestion in Feedback. On my side, I think I'm lucky (hope it will last). My last 20 or more submissions were all processed in less than 12 hours.

@Autodeal, you close your thread, which likely mean you do not expect any answer anymore on the forum ?

Have you checked that all certificates are still valid ?

@tomgreef so you have the infoPlist, but I do not see Root files. Here is what I get in my projects: