SO, there have been a lot of different issued raised and I've got limit time to reply on this, so I'm going to focus on the details that I think can be most useful.
macOS 15.1 was officially released one or two days ago
As you might imagine, the process of managing releases is extremely complicated, but the basic "pattern" is that which bug fixes will be included in a given release heavily depends on the particular focus of that release, how much time is left in it's test cycle, and how risky the fix is considered. Those factors mean that it's common that a fix cannot be included in a given release because any new fix is considered to risk late in the beat cycle.
Note that a similar pattern also happens when a build is early in the seed/release process so, for example, I would expect additional bug fixed to be included in macOS 15.2 (24C5057p). Related to that point, significant testing occurs between the time a given build is created and when it's released as a seed build. It's not unusual for a fix that will be included in the "next" seed release to have already been integrated well before the "current" seed is actually released.
All of this is to try and explain why the fact that the fix was not included in 15.1 or 15.2 (24C5057p) does not mean the bug isn't being addressed.
Yeah I don't understand why they have to speak to us in riddles.
In terms of the App Review rejection, there are a few things I want to clarify:
So now, according to the Apple Store Connect reviewer, the Finder Sync extensions settings missing from System Settings in Sequoia is a bug in MY application!
In general, App Review's testing is user oriented. That is, they're using your app as a typical user would and reporting any problem they find. There role isn't really to determine why a particular failure occurred, it's to report any problem they find.
@Kevin, I understand that your "role is primarily about communicating with us, not bring information "back" to Apple. While you can and do work very closely with your engineering teams, that's not your primary role
While I hope you don't find yourself dealing with this sort of situation again, for future reference, the best thing you can do for an App Review issue like is appeal that rejection and, as part of that rejection, provide as much information as possible back to the reviewer, particularly conversation like this thread and the names of any Apple employees who might have been involved (in this case, "me"). Apple takes privacy very seriously and that extends to information about developers, the bugs they file, and the apps they work on. It's much easier for App Review to contact me about a review issue with a particular app than it is for me to try and track down an app that's been rejected based on bug report information. I was able eventually able to track down your submission and made sure the relevant teams understand exactly what's going on.
__
Kevin Elliott
DTS Engineer, CoreOS/Hardware
