Thanks for the reply, but frankly, this entire roll out of Acrobat DC is putting us, as longtime Adobe partners, and developers of both Acrobat and InDesign plug-ins, as well as resellers of the PDF Library, in an impossible position.
You say that you "shipped" it to customers. But what you really did was have it automatically "upgrade" from Acrobat XI for all CC users, regardless of whether third-party plug-ins were compatible with the new version or not.
I must have missed your announcement from a month ago. Exactly where did you announce it? More importantly, how did you communicate it to plug-in developers? I've been regularly searching for "Acrobat 12" and "Acrobat CC" and not finding anything definitive. (Apparently I did a bad job of guessing what the new name would be.)
More specifically, when did you communicate to plug-in developers that the new Mac release would be 64-bit only? It shouldn't surprise you that most plug-ins are currently built as 32-bit, and that the switch from 32-bit to 64-bit on Mac is not trivial, since many of us are using older technologies such as Carbon, which are not available in 64-bit.
Why are we still using Carbon, you might ask? Well, maybe it has something to do with the fact that functions such as AVPageViewAcquireMachinePort (and AVPageViewAcquireDrawContext) return a Carbon GrafPtr on Mac. (By the way, you guys broke those drawing functions in Acrobat 11.0.4 for Retina displays.)
So how are we supposed to do custom drawing in a plug-in for the 64-bit-only Acrobat DC without Carbon? I guess we'll have to wait 30 days for the new SDK. Then we can start figuring out how to port everything to Cocoa or whatever the new way of drawing in the new SDK is. So when our* customers follow your advice to "contact the respective plugin developer and obtain a 64-bit version of the plugin", we'll just tell them, "Sorry, we're waiting for Adobe to provide us with what we need. Call back in a month."
* They're "our" customers, but each copy of our VDP composition plug-in not only catalyzes a sale of Acrobat (and InDesign), it also ships with a licensed copy of the Adobe PDF Library. So they're really YOUR customers as well, on multiple fronts.
Perhaps this is a sign that, instead of an Acrobat plug-in, we should just build standalone Windows and Mac apps, or even a web app, so that our users can design their VDP templates without Acrobat (or InDesign). And instead of composing locally, we should just have all compositions occur on a remote server, so that we don't have to sell a copy of the PDF Library with each copy of the design tool. This is probably a good strategy for us anyway, as we prepare to ramp up sales efforts in Europe and Asia, where we hope to have many thousands more sales. Not requiring Acrobat or the PDF Library with all those sales might be better for us, but I don't think it will be better for Adobe.
So even though Adobe doesn't seem to care about how this DC "upgrade" roll out is making life difficult for both users of Acrobat and plug-in developers, I would think someone there would care about losing Acrobat and PDF Library sales.