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.
Xamarin.iOS 22.214.171.1248 (current alpha channel release) is showing this issue where it says "Could not AOT the assembly '.../SQLitePCL.raw.dll'"
I "Undefined symbols for architecture arm64" for a lot of symbols, for example:
Undefined symbols for architecture arm64:
"_sqlite3_aggregate_context", referenced from:
wrapper_managed_to_native_SQLitePCL_SQLite3Provider_NativeMethods_sqlite3_aggregate_context_intptr_int in SQLitePCL-b3b83a.o
Here's a more complete list: https://gist.github.com/bratsche/039bc47f00eaa3af145e1b081a8e40b6
If I go back to the beta channel (version 126.96.36.199) then the problem goes away.
This should be reproducible using any project that uses Akavache with SQLite. I can make a repro project if you need one.
Thanks for the bug report, while it seems pretty straight forward to repro, could you attach a test case for this? This way we will have the same code and we can avoid the possible guessing work.
Thanks in advance!
That's because the symbols do not exists on the platform. See #42416  for a workaround. We'll relax this requirement on a future alpha but, in some cases it's just not possible to link to non-existing symbols.
*** This bug has been marked as a duplicate of bug 42416 ***