App Wrapper Steps for NON-MAS packaging?

Why not just read the Dropbox.app’s configuration?

[quote]~/.dropbox/
~/.dropbox/info.json
~/.dropbox/dropbox.pid[/quote]
Then check: is path configured (and affecting “me”), and is the dropbox process running (otherwise it shouldn’t inferfere with what you’re up to)?

Walk the destination path and look for .dropbox and .dropbox.cache.
(EDIT - like Jürg said :slight_smile: )

How did I miss that? :slight_smile:
You’re right - there’s another .dropbox file in the “Dropbox-Folder root”.
So combine the two ideas and you get a quite a nice solution :slight_smile:

Thanks guys, really useful information. :slight_smile:

So now it checks to see if Dropbox is running, if so it then reads the DropBox data file and finds the path of the DropBox folders (to which there can be multiple). Then it checks to see if the current folder is within one of those folders…

http://www.ohanaware.com/appwrapper/appWrapper37Alpha.dmg

I don’t know how sign the single files contained in xojo desktop app.tar file using app wrapper.
It signs only dmg

[quote=355529:@Marco Ilardi]I don’t know how sign the single files contained in xojo desktop app.tar file using app wrapper.
It signs only dmg[/quote]
It sounds like you’re compiling on Windows, you need unpack the .tar file on macOS and then drag the application into App Wrapper.

The most popular way to distribute a macOS application outside of the App Store is to create a DMG file. There’s a bunch of different ways to create a DMG file, DMGCanvas is the most popular app.

i’ve solved thank you