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.

What do you expect other developers to do on this ? Nothing, as the forum is not an official channel to Apple. You should contact Apple support directly.

Sorry, whatever the interest, this has nothing to do in the developers forum. You are trying to engage in a contractual agreement with Apple, so proceed directly with Apple. Developers here don't need to be involved. Have a good day.

Only you can tell what is in your code. So advice is to analyse why reviewer concluded that: your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences They give you some hints. Did you analyse ?

3 months with no reply is not normal. Did you received at least a mail stating that your app was waiting for review ? If no, that means you have not in fact submitted your app. Submitting has 2 steps: once you have completed all the informations in AppStoreConnect, you click a button to send for review (I don't remember the exact text of the button) then the button's title change to something like "ask for review": you have to click again. In the following minutes you'll receive a mail stating that your App is Ready for Review.

Have a look here: https://discussions.apple.com/thread/256078060?sortBy=rank and here: https://support.apple.com/en-us/108763 But I would be cautious without a backup. So, you may also wait (a couple of months) for an iOS 26 release and upgrade at that time. Your data should be safe. Then, don't forget to make a backup.

You should post a bug report. If enough people request it, may be it could come back ? Otherwise, it is likely than an app will be available with the same and even extended capabilities. Maybe a good app idea for you ? 😉

The fact that the app was rejected several times probably doesn't help to speed up review. Did you indicate clearly, in the notes to reviewer, what you explain here ? As a different reviewer may be reviewing the app, that will help him or her to understand the context and not just notice that the app was already rejected 3 times. PS: please note that the developers' forum is not an official channel to Apple, even less to the review team.