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.
Created attachment 25334 [details]
Error on attempting to open Designer for iOS & Android projects.
1. Create an iOS / Android project.
2. Connect XMA.
3. Attempt to open designer by double clicking on the StoryBoard file.
4. Attempt to open designer by double clicking on the Android designer file.
StoryBoard and Android Designer file should open successfully.
Error dialogue stating "Exception has been thrown by the target of an invocation" seen on trying to open the designer file.
- Microsoft Visual Studio Enterprise 2015
- Version 14.0.25123.00 Update 2
- Microsoft .NET Framework Version 4.6.01586
- Xamarin 22.214.171.1246 (8d20b19dd)
- Xamarin.Android 126.96.36.199 (f241f51)
- Xamarin.Android SDK 188.8.131.52 (HEAD/f241f51c6)
- Xamarin.iOS 184.108.40.206 (75235cd)
Detailed build info:
Test Plan link:
Test Case Link:
Happens Every Time (100%)
Regression from Previous Milestone
Xamarin V 220.127.116.11
IDE Logs attached
VSTS Bug Link: https://devdiv.visualstudio.com/DevDiv/XamarinVS/_workitems?id=508109&_a=edit
These are two separate issues.
This looks like a bug which can break the android designer. It would need to be filed separately against the Android component of XVS:
> System.NullReferenceException: Object reference not set to an instance of an object.
> at Xamarin.VisualStudio.Android.CommandHandlers.GetSdkInfoCommandHandler.ConvertFramework(AndroidFramework x) in C:\d\lanes\5409\8d20b19d\source\xamarinvs\src\Core\VisualStudio.Android\CommandHandlers\GetSdkInfoCommandHandler.cs:line 43
> at Xamarin.VisualStudio.Android.CommandHandlers.GetSdkInfoCommandHandler.Execute(GetSdkInfo command) in C:\d\lanes\5409\8d20b19d\source\xamarinvs\src\Core\VisualStudio.Android\CommandHandlers\GetSdkInfoCommandHandler.cs:line 28
There's an issue in inspector which could break the ios designer because it'd break events from being raised correctly:
> System.ArgumentNullException: Value cannot be null.
> Parameter name: path4
> at System.IO.Path.Combine(String path1, String path2, String path3, String path4)
> at Xamarin.VisualStudio.Inspector.XamarinInspectorPackage.<RemoteServerProvider_ServerConnected>d__19.MoveNext() in C:\d\lanes\5409\8d20b19d\source\xamarinvs\src\Features\VisualStudio.Inspector\Vsix\XamarinInspectorPackage.cs:line 158
This issue should be filed against Inspector.
The issue you're experienced in the screencast does not look like an ios designer bug. I believe the workaround I was given before is to right click on the file and choose 'open with' and then choose the ios designer. Does this fix the problem for you?
We should still file those other two issues as actual bugs as they are problems which need addressing :)
Can anyone confirm that the two issues above were filed, and also that the workaround did work? If so there are no designer bugs here, but there are issues which can negatively affect and break the designer which absolutely should be addressed!
No, the above two issues have yet to be filed. The Global Logic team has been out on holiday, and thus unable to follow up. Mohak and I discussed this a bit, and he will be filing these issues upon his return.
Just chatted to Mohak - it looks like all the files were installed but sometihng is wrong wrong.
There's nothing in the main log and there are no designer logs. We need working logging to diagnose this, or someone needs to help figure out what's going wrong.
If you look at the other log files attached there are many worrying looking exceptions which could be affecting us, such as:
System.> System.NullReferenceException: Object reference not set to an instance of an object.
> at Xamarin.Messaging.Integration.State.AgentsStartingState.ReportAgentFailure(AgentInfo agentInfo, IMessagingAnalyticsAggregator analytics, Exception ex, Nullable`1 progress) in C:\d\lanes\5409\8d20b19d\source\xamarinvs\External\messaging\src\Xamarin.Messaging.Integration\State\AgentsStartingState.cs:line 112
> at Xamarin.Messaging.Integration.State.AgentsStartingState.<StartAgentAsync>d__15.MoveNext() in C:\d\lanes\5409\8d20b19d\source\xamarinvs\External\messaging\src\Xamarin.Messaging.Integration\State\AgentsStartingState.cs:line 95
> --- End of stack trace from previous location where exception was thrown ---
> at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
> at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
> at Xamarin.Messaging.Integration.State.AgentsStartingState.<OnExecutingAsync>d__14.MoveNext() in C:\d\lanes\5409\8d20b19d\source\xamarinvs\External\messaging\src\Xamarin.Messaging.Integration\State\AgentsStartingState.cs:line 61
> Xamarin.Messaging.Integration.State.AgentsStartingState|Error|0|An error occured starting the Build 18.104.22.1686 agent: Object reference not set to an instance of an object.
That should also be filed in addition to the other two issues. For now we need more information about what's throwing the exception to properly deal with the issue.
Marking this as 'confirmed' for now. There are many worrying exceptions in the logs which could cause issues, but as of yet there is nothing specifically designer related showing up anywhere.
It is likely we will simply close this bug in the near future with no action taken on our part.
Have all the bugs which I've indicated in previous comments been filed and investigated? Some of those are blockers.
To re-iterate: There are bugs in the logs which can break the designer. They could've caused this, or it could've been something else.
There is no known action we can take on our side so once the other bugs are filed we can close this.
Thanks. I’ll just close this then.