Yes, behaviour is "surprising". I had noticed other issues, like the content of a segment being hidden during move. Did you file a bug report ?

You'd better first contact support. Did you do it ?

Could you explain what you mean by "more architectures" ? Do you mean target more platforms ? Which ?

Guideline 4.3 is pretty explicit: Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase. That seem to be precisely your case. Another thought: I don't know if it is the cause, but there is a Babbel app to train for foreign languages. The name of your app appears pretty close to it.

You should contact support. They should find out what is blocking (may be some information missing ?). Did you receive an email stating that app was Ready for review ?

That's not a question for the developers' forum. Go to Apple support instead or file a bug report.

You should add a comment to reviewer in your submission, explaining what you say here. Maybe that will help pass the 4.3b rejection. You could also contact support by mail to get more help.

Welcome to the forum. You wrote: It was reviewed on July 15, 2025. Was it reviewed or just submitted ? Please explain precisely what you've done so far. Is it the first submission ?

Do you mean protobuf ? If so, you could have a look here: https://medium.com/@andy.nguyen.1993/protobuf-in-swift-809658ecdb22

All content is now original (graphics, UI, icons, name, etc.) Do you mean it was not in earlier submissions ?   The same version was already approved on Google Play That's never been an argument for Appstore approval. They have their own rules which may be stricter than other platform's.   We've removed anything that could even theoretically be misinterpreted as copycat content Could you detail ?, That may have caused previous rejections.   the app “appears to misrepresent itself,” That's what you have to understand. How do you describe the app ? What you can do is attach those comments in the notes to reviewer for a new submission. That may help, unless there is effectively something reviewers have found that violates guideline 4.1.

I tested in iOS 26.0 simulator. Search works properly. So, explain precisely what does not work. Did it work in beta 2 ? If so, you'd better file a bug report.

Is BSAuditToken a class you defined ? If so, did you implemented supportsSecureCoding as instructed in the error message ?

I tested the code in Xcode 16.4. I can select colors (but only one by one). It seems to work So could you explicit very clearly what the problem is (are) ? With more details than a single sentence.   buttons on Loader don't update the list on the screen for one Could you explain (possibly with some screenshots) ?   dealing with deleting choices that are in use - how does picker deal with them? Same question: Could you explain (possibly with some screenshots) ? Could you show where set / array is an issue in your code ?

Is it something new to Xcode 26 or are you using Xcode 16 ? You're right, that's a pretty common issue with SwiftUI and the pain is that there is not hint where the "error" precisely is. That's intrinsic to how SwiftUI works (it is not a compile error but a run time error). In some cases, just adding an element in an addition can cause the problem. I do not usually break it up. A common issue is with arithmetic expressions: always make sure that the type of each value is explicit. To localise the error, I go by dichotomy. I comment out half of the suspect part of code. If it works, problem is likely form the commented out. Otherwise, I comment half of the remaining part, and so on until I get to a single line.