This is directed at @Sam Rowlands, but I thought everyone could learn from the answer.
Do you have an App Wrapper 3 guide for those of us wishing to create a PKG/DMG that is NOT destined for the MAS? There are so many options that are aimed at MAS, and I don’t know which I need to worry about for non-MAS wrapping.
In the General tab, in the code signature box, click on the box and turn OFF “Show All certificates” Now you should have, if your certs are correct, a GateKeeper and App Store. Select the GateKeeper. Under the capabilities tab, turn OFF Sandboxing. Now everything else on this tab is not apropos. The info and Other tabs you should fill out as appropriate for your app. In the signing process, App Wrapper will let you know if the signed app passes GateKeeper
Just a note, you don’t have to disable sandboxing for non-mas apps.
If you’re distributing in both locations (mas and outside) you can leave all your settings the same, just sign with the correct certificate for your distribution method.
Yep - all of the command line bits are done with 2007r1 so that they can share a Libs folder rather than needing to have 11 copies of the same libraries. Glad I’m not interested in selling these on the MAS.
[quote=316443:@Tim Jones]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[/quote]
A newer version of App Wrapper will use a different identity selector that will make it more obvious when the certs are missing.
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.
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.
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.
Amazingly enough, I have a significant number of users who visit the web site, but purchase on the MAS. I also have a couple apps that do not sell at all direct (like zero sales in six month), and have a nice little life in the MAS.
I always appreciate your input Michel, in this case it helps provide some perspective.
I’ve done some digging and can find that apps such as our Card making app and Iconographer do better on the App Store, while our latest Photography application is doing better on our own site. The photography application is the most expensive of these 3.
I accredit the photo apps success on our site to several factors:
Trial version, so people can try before buying.
Upgrade pricing, so previous customers of the application can get the newer version at a discounted price.
I think it would be a fair test if both of these options were available on the Mac App Store.