No, just the symbol table in the binaries. You can easily do it yourself with the 'nm' command. It seems that they are using a tool that matches the 'nm' output with a list of private APIs since about a month or so, meaning that a lot of updates suddenly get rejected like this. What really annoys me as a developer though, is that they should be able to automate this check and give feedback instantly. (It's not like they will give feedback on more than one 'problem' anyway.) Instead you'll still have to sit out the 2 week waiting period.

Seriously if they are so hung up on undocumented API calls, they should just implement that check as part of the binary upload process. Run the binary through an automated flagging system. This will not only benefit developers but also cut their review time plus reduce the number of update submission indirectly.

This lack seems a symptom of what pg is describing - they are no longer getting the best and brightest programmers around.

Or simply give you the list so you can check your binaries yourself! Of course the list might change frequently but it would save everyone time and grief.

They document what you can do. If you are stepping outside those boundaries, why do you blame Apple for your grief and wasted time? You agreed not to do that when signing up in the first place.