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 on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I add Akavache on my share and iOS project.
I don't have problem with the share project but since I add the package akavache.sqlite3 (he is mandatory to use akavache) I have this error :
MTOUCH: error MT3001: Could not AOT the assembly '/Users/[...]/Documents/dev/[...]/[...]/ac/Ac.Touch/obj/iPhone/Debug/build-iphone8.2-10.2.1/mtouch-cache/Build/SQLitePCLRaw.batteries_e_sqlite3.dll'
You can reproduce it with a project where you add akavache and all the package related (akavache.core & akavache.sqlite3).
I try to remove the incremental building but it doesn't change any thing...
Can't reproduce this. What xamarin.ios version does this happen with ?
I am also unable to reproduce the build error.
Please include your full build logs, crash reports (if any), test case (to reproduce) and all version informations.
The easiest way to get exact version information is to use the "Xamarin Studio" menu, "About Xamarin Studio" item, "Show Details" button and copy/paste the version informations (you can use the "Copy Information" button).
Can you please provide the information requested by Tim.
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!