Bug 23650 (Markus) - Storyboard crashes often when inserting images on tab bar
Summary: Storyboard crashes often when inserting images on tab bar
Status: RESOLVED NORESPONSE
Alias: Markus
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-10-06 12:52 UTC by Markus
Modified: 2014-11-11 06:04 UTC (History)
7 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Stack (79.64 KB, text/plain)
2014-10-06 12:52 UTC, Markus
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED NORESPONSE

Description Markus 2014-10-06 12:52:20 UTC
Created attachment 8317 [details]
Stack

When inserting an image on the tab bar I get:

System.AggregateException: One or more errors occurred. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
   at System.Net.HttpWebRequest.GetResponse()
   at MonoTouch.Tools.Utilities.BuildServerClient.ServerIO.Server_Post(String command, MemoryStream ms, IDictionary`2 queryVariables)
   at MonoTouch.Tools.Utilities.BuildServerClient.<>c__DisplayClass12.<ExecuteRawPostCommand>b__11()
   at MonoTouch.Tools.Utilities.BuildServerClient.ExecuteCommandTask[TResult](BuildServerCommand command, Func`1 code, Boolean propagateExceptions)
   at MonoTouch.Tools.Utilities.BuildServerClient.ExecuteRawPostCommand(String commandName, MemoryStream stream, IDictionary`2 queryVariables, Boolean propagateExceptions)
   at Xamarin.VisualStudio.IOS.Utilities.VSBuildServerClient.DesignerSendPayload(MemoryStream payload, IDictionary`2 queryVariables, Boolean propagateExceptions)
   at Xamarin.VisualStudio.IOS.Designer.DesignerRemoteRequests.<>c__DisplayClass3.
 
For full stack trace see attachment.
Comment 1 Tajinder Singh 2014-10-07 03:55:48 UTC
I have tried to reproduce this Issue with current stable builds but I am not seeing this crash. This is the screencast for the same: http://www.screencast.com/t/rdiDZCVt2

Checked with following builds:

X.S 5.5 (Build 227)
Git revision: 7b721eeec7a2fa4c4f4de0ecd2aed4dc25edac95
X.iOS 8.2.0.193

@Markus, Could you please check it again with latest stable builds and provide me screencast of the steps of Issue which you are getting?
Comment 2 Markus 2014-10-07 04:07:25 UTC
Sorry - this is in Visual Studio, not Xamarin Studio.
Comment 3 Alan McGovern 2014-10-07 10:54:15 UTC
You are hitting one of three known issues. Two of which we have patches for, one of which we are actively investigating. In order to figure out which of the three known issues it is (or if it's a fourth unknown issue) we'll need all the log files.

Can you follow the instructions here http://kb.xamarin.com/customer/portal/articles/1675684-how-to-collect-version-information-and-logs to gather the mac build host logs and version information.

Secondly, can you open Console.app and see if there are any crash logs for 'mtbs' in the User Diagnostic Reports' section ( http://screencast.com/t/0ddCMf1Eq7 ). If there are can you attach those too?
Comment 4 Alan McGovern 2014-11-11 06:04:07 UTC
If you can provide further information, feel free to re-open the bug and attach it. Otherwise I'll just assume that you were hitting one of the known issues which we've already fixed as that is the most likely scenario.

Thanks!