[sword-devel] MacSword and Mac AppStore
niccarter at mac.com
Sat Jan 29 05:16:14 MST 2011
You should be able to explain away #1 - this is exactly what all Bible Apps do, so unless there are no other Bible Study apps available, you should be able to explain this. I'd read up carefully that point, cause you're not installing code & it depends on their definition of "resources"... I know they relaxed that point heaps recently, but that was for iOS - is it different for the Mac store vs the iOS store? :(
For #3, the file system is very different under iOS - I can only play with the filesystem within my own little sandbox & hence I oblige... ;) probably worth complying for that & surely you can add code to migrate any/all modules across on launch? Or something? :(
For #2, it may be worth having 2 versions of the app, as I think the additional exposure of the Mac App Store would more than make up for having an extra build in Xcode... So you can put your sparkle code back in there, too... :)
I have heard of developers having different builds of all their apps - one for their existing customers & so they get the free upgrades they were promised & one for their App Store customers, as you can't migrate your customers licences across to the App Store at this point in time...
Hope that helps? :)
Sent from my phone, hence this email may be short...
On 29/01/2011, at 11:02 PM, Manfred Bergmann <manfred.bergmann at me.com> wrote:
> Hi Guys.
> I think it is relatively unlikely to succeed putting MacSword/Eloquent in the Mac AppStore.
> The main stumbling blocks are:
> - the module installer:
> Apple doesn't allow "Apps that download or install additional code or resources to add functionality or change their primary purpose will be rejected"
> - creating the links for the module utilities in /usr/local/bin. For that we aquire admin priviledges via an Apple API but allow doesn't allow that either:
> "Apps that request escalation to root privileges or use setuid attributes will be rejected"
> - finally Apps are only allowed to create folders in the filesystem that reflect the name of the App. We create a "Sword" folder where the modules are stored.
> Apple says we do not "comply with the Mac OS X File System documentation".
> Nic, did you have similar issues (module installer and filesystem)?
> I'm not willing to remove this from the App and If Apple doesn't except explanations for those then AppStore is a "no go".
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel