@Tim J Ah - my non-MAS cert is not showing up. This is why I keep seeing the MAS submission options. Looks as if my call with Apple sorted the MAS certs, but did nothing to return my non-MAS certs...
More digging :S
A newer version of App Wrapper will use a different identity selector that will make it more obvious when the certs are missing.
@Tim J Does anyone know how to get codesign to tell you WHICH files contain the unallowed "resource fork, Finder information, or similar detritus"?
Currently there isn't.
Code sign simply fails stating that some files have this crap (which in some cases Finder magics ads for you).
App Wrapper doesn't bother checking in it's main function, it simply blasts everything that it's aware of. In a secondary function, it does check each and every single file (which is why it's a little slow at the moment), but this is carried out _after_ the main function, as in some situations (DropBox) there is still meta data after App Wrapper has removed it. A future version will refuse to wrap to a DropBox folder.
@Tim J It appears to be related to the fact that some of my helpers use a hook into the QuickTime stuff. I'm looking into that since I don't use any audio or movie players in the particular app.
Older versions of Xojo link to Quicktime or QTKit in the Xojo.framework, these are strictly prohibited on the Mac App Store now. Yet apps that use Quicktime continue to work fine.
@Tim J Glad I'm not interested in selling these on the MAS.
After my experience, I've been seeing articles from various sites reflecting pretty much the same thing. Apple's lack of interest in the App Store and crippling requirements have not only pushed developers away from the App Store, but even consumers (especially pro-sumers) have given up and now using Google to find apps that they need.