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.
Created attachment 23996 [details]
Visual studio details
When I try to archive my iOS project for publishing if I select "link Framework SDKs only" as Linker behaviour I have the following error
MTOUCH : error MT2001: Could not link assemblies.
Method: `System.Void Mobile.Core.DL.DatabaseProxy/<CreateTablesAsync>c__async0/<CreateTablesAsync>c__AnonStorey1E::<>m__0()`
Assembly: `Mobile.Core, Version=1.0.6424.17905, Culture=neutral, PublicKeyToken=null`
Reason: Value cannot be null.
Parameter name: instruction
Value cannot be null.
Parameter name: instruction
Done building target "_CompileToNative" in project "FleetMobile.iOS.csproj" -- FAILED.
Done building project "FleetMobile.iOS.csproj" -- FAILED.
Everything works fine I select "Don't link"
Attached the infos related to Visual studio I am using
Could you please provide a full build log using the additional mtouch arguments '-v -v -v -v -v'?
A simple repro case would also be helpful if you are able to provide one.
Created attachment 24014 [details]
Extended build log
Attached the extended build log
Try rebuilding or updating your `Mobile.Core.dll`, it looks like the debugging symbols are bad or out-of-sync.
This should be better reported in our next version. However this can be multiple causes for this. Can you attach a zip containing Mobile.Core.dll and the .pdb or .mdb associated files ? We'll test to make sure that case was covered. Thanks!
It looks like the clean didn't delete the old files
We have deleted it manually
Now it works
Good news :) but I'm curious how this could happen.
From your logs it seems that `Mobile.Core.dll` is not build from that solution, right ?
It seems the origin of the files (being copied to your project) has both the old (mdb) and new (portable pdb).
> It looks like the clean didn't delete the old files
A clean of your solution (the one from the logs) won't be cleaning external/input files, only the files it produce.
> We have deleted it manually
From the logs there are also other assemblies with both mdb and pdb files.
@Jeff the logs shows some files (like the debugging symbols) are copied twice, is that a known issue ? If not I'll file another bug for it.
@JB it's an older version (15.2) of cecil but I wondered if you have some tests in cecil where both an mdb and pdb are provided.
Yes, Mobile.Core.dll is not build from that solution.
We have another project with mobile.core and with other internal library for Android and iOS
After building them we copy all files in this new project and we reference this dll files
When I have tried to launch a test app in the solution with Mobile.Core I see that xamarin debugger not hitting the breakpoint
After cleaning my solution I check some files as Mobile.Core dll/mdb were left on the disk in obj and debug in obj/debug and bin/debug and /release.
The other libraries was totally cleaned (only some files in obj are not deleted)
I have deleted it in Finder(mac), rebuild solution and I have copied the new files in the second project
The second project works again. It has been repaired.
if it happens again please reopen, thanks for the provided information!