Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 18930 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
First an explanation of the issue that was encountered:
Client made a Mac app installer package. When this was installed initially into the Applications folder, the SQLite database was inaccessible due to an error accessing libsqlite3.0.dylib, which was added as a native reference to the app project. After some investigation, it seemed to be a permissions issue and that changing the ownership of all of the files in the .app package to owner user, group admin, allowed the app to function properly. The client then discovered that the libsqlite3.0.dylib in his app project had No Access in the permissions for Everyone. See desk case noted in original comment above for details. The client then changed the permissions to Read Only for Everyone and everything worked as expected.
So the enhancement request would be to add a check, if possible, to make sure that references in the app project have the permissions they need.
The solution to this probably depends on where the libsqlite3.0.dylib is coming from...
if it is being included by the Xamarin.Mac packager (aka mmp), then yea, it should probably make sure the permissions for those libs are appropriate.
However, if libsqlite3.0.dylib is being copied into the app bundle as part of the project itself, then the developer probably needs to set the appropriate permissions.
Not sure we want to be going behind the developer's back by overriding his/her permissions.
Yes, the libsqlite3.0.dylib was added as a native reference to his project. Sorry I did not make that more clear. And changing the permissions resolved the issue as noted on comment 1.
While the priority is low, it would not hurt to do this.