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 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.
With reference to my forum post at http://forums.xamarin.com/discussion/57072/debugging-own-private-nuget-packages
Using VS 2015 and the latest Xamarin 4 update, I'm unable to step into the source code of private nuget packages that I reference from my Xamarin Android project in VS 2015. These private nuget packages includes the pdb files. When I downgrade to Xamarin 3.11.1594.0 everything works as expected as I can successfully step into the source code of the nuget package from within my Android app project.
This sounds like a duplicate of Bug 35691.
Can you please try if the following patched build helps?
Please keep in mind that this is a custom build, it's 126.96.36.1998 (be53781) and as it's not official, it won't be public and it didn't passed the regular QA process.
Also, we're mostly going to publish a new build which matches this version number but differs in the hash: 188.8.131.528 (36f3cb2). That version includes other fixes, but doesn't include the fix for this issue. If this patched version helps, I would suggest you to don't upgrade until we release 4.0.1.x builds.
I'm resolving the bug as a duplicate, but please feel free to reopen it if you think that's not accurate, and the patch doesn't help.
*** This bug has been marked as a duplicate of bug 35691 ***
I'm a bit confused. It seems that the fix for Bug 35691 was already released in the latest service release cycle? I was testing using the latest service release (https://releases.xamarin.com/stable-release-cycle-6-service-release-0/) when I logged the bug. Can you confirm whether Bug 35691 was included or not?
W.r.t the patched build - we've wasted such a lot of time already with issues relating to the Xamarin 4 update that I loathe installing another update that hasn't gone thru a proper QA process. Sure, it might solve our issue but it might also introduce other regression bugs that will again hamper the team productivity. For now I'm asking the team to roll back to the latest stable Xamarin 3 update. We need to focus on building business functionality and can't afford to constantly fight our tools.
## Status update for any customers CC'd on the bug
Since Bug 35691 is marked as private, I will add a note here to record that the candidate fix for Bug 35691 is now included in the latest Alpha version of "Cycle 6 – Service Release 1" .