Comment 1 for bug 1418650

See
https://bugs.launchpad.net/inkscape/+bug/181639/comments/4
and also
https://bugs.launchpad.net/inkscape/+bug/793227/comments/2

It didn't really work with 0.48 either, you just happened to not rely on any file of the installed shared Inkscape resources. Due to changes unrelated to osx packaging, it is now (with 0.91) required to make sure that the current working directory is changed to the bundle top in the innermost launcher shell script (as detailed in the comments of the script).

Running '/Applications/Inkscape.app/Contents/Resources/bin/inkscape' directly as substitute for a regular command line installation of Inkscape on OS X was never recommended (instead, '/Applications/Inkscape.app/Contents/Resources/script' should have been used, with the same limitations wrt absolute path names for files specified as arguments on the command line).

If you need to run Inkscape via command line, I would recommend to install it as such (e.g. via MacPorts) - the current bundle structure has known limitations (it is based on legacy code to implement sort-of relocation support for osxapp-configure builds), and with 0.91 does require to always use absolute paths to files referenced on the command line (otherwise a necessary resource (units.xml) can't be loaded and this will affect e.g. export to bitmap as soon as a dimension or resolution is specified on the command line).

Linking as duplicate to bug #181639.