I am struggling with the same problem right now. The βanswerβ is that the ForVendor ID is broken down according to its intended design in Apple Documentation:
It is assumed that the packet identifier is in reverse DNS format, and the first two components are used to generate the provider identifier. For example, com.example.app1 and com.example.app2 will have the same provider identifier.
What is the reality of the situation that the ForVendor identifier is identical only for applications that use the same provisioning profile and signing certificate. As an example, I have several applications in my Enterprise environment, all of which are com.mycompany ..
identifierForVendor is identical for applications using bundleID com.mycompany.app1. * and its preparation profile, however com.mycompany.app2, using the same signature certificate, but a different preparation profile gives a different ForVendor identifier value.
EDIT: This only happens in iOS7, but works fine in iOS6. I tested this for some time yesterday and can duplicate the problem within 7 days, but within 6 I get the expected results.
EDIT2: Apple moved target messages by identifier ForVendor. They apparently identified their problem with the algorithm and, instead of fixing the problem, changed the functionality of the identifier between versions of iOS with a change in documentation. An updated documentation link is provided below. SMH.
identifierForVendor
source share