Visual Studio 2017 v15.9 Storyboard designer cannot connect to Mac while VS is connected to Mac
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Visual Studio 2017 v15.9 on Windows 10 has apparently a new bug: the storyboard designer cannot connect to Mac. Previously in 15.8, the storyboard could connect and many features are working fine, however the ImageView could not work properly. After upgrading to to VS 2017 v15.9, the storyboard editor could not connect to Mac thus could not be opened, while VS is actually connecting to Mac and is able to compile and debug and deploy iOS app to simulators and devices.
I am having Mac Mini and xcode 10.1, but no VS for Mac. It is easy to replicate: just create a new Xamarin app with iOS project. After compiling and testing in simulators running in mac to prove things are OK, then double click on either LaunchScreen.storyboard or Main.storyboard created by scaffolding, then the designer tries to connect to Mac and end up with error message: "The iOS Designer requires an active connection to a Mac server. Please connect to a Mac to enable the designer.".
Now all my iOS apps work however I could not alter any storyboard. I don't like modifying the XML directly in a text editor.
I had spent hours researching solutions or hacks, so far no luck. Do you have some ideas? Cheers.
ios xcode macos xamarin storyboard
add a comment |
Visual Studio 2017 v15.9 on Windows 10 has apparently a new bug: the storyboard designer cannot connect to Mac. Previously in 15.8, the storyboard could connect and many features are working fine, however the ImageView could not work properly. After upgrading to to VS 2017 v15.9, the storyboard editor could not connect to Mac thus could not be opened, while VS is actually connecting to Mac and is able to compile and debug and deploy iOS app to simulators and devices.
I am having Mac Mini and xcode 10.1, but no VS for Mac. It is easy to replicate: just create a new Xamarin app with iOS project. After compiling and testing in simulators running in mac to prove things are OK, then double click on either LaunchScreen.storyboard or Main.storyboard created by scaffolding, then the designer tries to connect to Mac and end up with error message: "The iOS Designer requires an active connection to a Mac server. Please connect to a Mac to enable the designer.".
Now all my iOS apps work however I could not alter any storyboard. I don't like modifying the XML directly in a text editor.
I had spent hours researching solutions or hacks, so far no luck. Do you have some ideas? Cheers.
ios xcode macos xamarin storyboard
My current workaround is to create a dummy project in xCode and use the storyboard editor there, and then manually copy the xml back to the Windows machine.Having to learn the strange UI of xcode, and whole process may be just slightly better than drafting xml.
– ZZZ
Nov 16 '18 at 20:06
add a comment |
Visual Studio 2017 v15.9 on Windows 10 has apparently a new bug: the storyboard designer cannot connect to Mac. Previously in 15.8, the storyboard could connect and many features are working fine, however the ImageView could not work properly. After upgrading to to VS 2017 v15.9, the storyboard editor could not connect to Mac thus could not be opened, while VS is actually connecting to Mac and is able to compile and debug and deploy iOS app to simulators and devices.
I am having Mac Mini and xcode 10.1, but no VS for Mac. It is easy to replicate: just create a new Xamarin app with iOS project. After compiling and testing in simulators running in mac to prove things are OK, then double click on either LaunchScreen.storyboard or Main.storyboard created by scaffolding, then the designer tries to connect to Mac and end up with error message: "The iOS Designer requires an active connection to a Mac server. Please connect to a Mac to enable the designer.".
Now all my iOS apps work however I could not alter any storyboard. I don't like modifying the XML directly in a text editor.
I had spent hours researching solutions or hacks, so far no luck. Do you have some ideas? Cheers.
ios xcode macos xamarin storyboard
Visual Studio 2017 v15.9 on Windows 10 has apparently a new bug: the storyboard designer cannot connect to Mac. Previously in 15.8, the storyboard could connect and many features are working fine, however the ImageView could not work properly. After upgrading to to VS 2017 v15.9, the storyboard editor could not connect to Mac thus could not be opened, while VS is actually connecting to Mac and is able to compile and debug and deploy iOS app to simulators and devices.
I am having Mac Mini and xcode 10.1, but no VS for Mac. It is easy to replicate: just create a new Xamarin app with iOS project. After compiling and testing in simulators running in mac to prove things are OK, then double click on either LaunchScreen.storyboard or Main.storyboard created by scaffolding, then the designer tries to connect to Mac and end up with error message: "The iOS Designer requires an active connection to a Mac server. Please connect to a Mac to enable the designer.".
Now all my iOS apps work however I could not alter any storyboard. I don't like modifying the XML directly in a text editor.
I had spent hours researching solutions or hacks, so far no luck. Do you have some ideas? Cheers.
ios xcode macos xamarin storyboard
ios xcode macos xamarin storyboard
edited Nov 16 '18 at 10:44
ZZZ
asked Nov 16 '18 at 10:34
ZZZZZZ
1,78911424
1,78911424
My current workaround is to create a dummy project in xCode and use the storyboard editor there, and then manually copy the xml back to the Windows machine.Having to learn the strange UI of xcode, and whole process may be just slightly better than drafting xml.
– ZZZ
Nov 16 '18 at 20:06
add a comment |
My current workaround is to create a dummy project in xCode and use the storyboard editor there, and then manually copy the xml back to the Windows machine.Having to learn the strange UI of xcode, and whole process may be just slightly better than drafting xml.
– ZZZ
Nov 16 '18 at 20:06
My current workaround is to create a dummy project in xCode and use the storyboard editor there, and then manually copy the xml back to the Windows machine.Having to learn the strange UI of xcode, and whole process may be just slightly better than drafting xml.
– ZZZ
Nov 16 '18 at 20:06
My current workaround is to create a dummy project in xCode and use the storyboard editor there, and then manually copy the xml back to the Windows machine.Having to learn the strange UI of xcode, and whole process may be just slightly better than drafting xml.
– ZZZ
Nov 16 '18 at 20:06
add a comment |
1 Answer
1
active
oldest
votes
Here is a problem report that matches your bug description.
Visual Studio 15.9.2 has just been released, so try updating Visual Studio.
Here is a snippet of the Visual Studio 15.9.2 release notes:
Issues Fixed in 15.9.2
- Xamarin iOS designer not working with 15.9 and Xamarin.iOS 12.2.1.10.
thanks for the update. I haven't updated to 15.9.2 yet still with 15.9. However this morning when connecting to Mac from Windows, VS 2017 updated the mono lib in xcode to the latest. Previously I had done such update to latest mono manually in Mac, however, VS reported implementable issue so I had to reverse back. Very strange. I will be checking soon and report back here.
– ZZZ
Nov 22 '18 at 2:52
1
confirmed that 15.9.2 fixes the problem. Hopefully such bug won't come back as it had reappeared a few times in last few years for different causes.
– ZZZ
Nov 23 '18 at 4:19
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53336066%2fvisual-studio-2017-v15-9-storyboard-designer-cannot-connect-to-mac-while-vs-is-c%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Here is a problem report that matches your bug description.
Visual Studio 15.9.2 has just been released, so try updating Visual Studio.
Here is a snippet of the Visual Studio 15.9.2 release notes:
Issues Fixed in 15.9.2
- Xamarin iOS designer not working with 15.9 and Xamarin.iOS 12.2.1.10.
thanks for the update. I haven't updated to 15.9.2 yet still with 15.9. However this morning when connecting to Mac from Windows, VS 2017 updated the mono lib in xcode to the latest. Previously I had done such update to latest mono manually in Mac, however, VS reported implementable issue so I had to reverse back. Very strange. I will be checking soon and report back here.
– ZZZ
Nov 22 '18 at 2:52
1
confirmed that 15.9.2 fixes the problem. Hopefully such bug won't come back as it had reappeared a few times in last few years for different causes.
– ZZZ
Nov 23 '18 at 4:19
add a comment |
Here is a problem report that matches your bug description.
Visual Studio 15.9.2 has just been released, so try updating Visual Studio.
Here is a snippet of the Visual Studio 15.9.2 release notes:
Issues Fixed in 15.9.2
- Xamarin iOS designer not working with 15.9 and Xamarin.iOS 12.2.1.10.
thanks for the update. I haven't updated to 15.9.2 yet still with 15.9. However this morning when connecting to Mac from Windows, VS 2017 updated the mono lib in xcode to the latest. Previously I had done such update to latest mono manually in Mac, however, VS reported implementable issue so I had to reverse back. Very strange. I will be checking soon and report back here.
– ZZZ
Nov 22 '18 at 2:52
1
confirmed that 15.9.2 fixes the problem. Hopefully such bug won't come back as it had reappeared a few times in last few years for different causes.
– ZZZ
Nov 23 '18 at 4:19
add a comment |
Here is a problem report that matches your bug description.
Visual Studio 15.9.2 has just been released, so try updating Visual Studio.
Here is a snippet of the Visual Studio 15.9.2 release notes:
Issues Fixed in 15.9.2
- Xamarin iOS designer not working with 15.9 and Xamarin.iOS 12.2.1.10.
Here is a problem report that matches your bug description.
Visual Studio 15.9.2 has just been released, so try updating Visual Studio.
Here is a snippet of the Visual Studio 15.9.2 release notes:
Issues Fixed in 15.9.2
- Xamarin iOS designer not working with 15.9 and Xamarin.iOS 12.2.1.10.
answered Nov 20 '18 at 21:15
Larry TrutterLarry Trutter
36144
36144
thanks for the update. I haven't updated to 15.9.2 yet still with 15.9. However this morning when connecting to Mac from Windows, VS 2017 updated the mono lib in xcode to the latest. Previously I had done such update to latest mono manually in Mac, however, VS reported implementable issue so I had to reverse back. Very strange. I will be checking soon and report back here.
– ZZZ
Nov 22 '18 at 2:52
1
confirmed that 15.9.2 fixes the problem. Hopefully such bug won't come back as it had reappeared a few times in last few years for different causes.
– ZZZ
Nov 23 '18 at 4:19
add a comment |
thanks for the update. I haven't updated to 15.9.2 yet still with 15.9. However this morning when connecting to Mac from Windows, VS 2017 updated the mono lib in xcode to the latest. Previously I had done such update to latest mono manually in Mac, however, VS reported implementable issue so I had to reverse back. Very strange. I will be checking soon and report back here.
– ZZZ
Nov 22 '18 at 2:52
1
confirmed that 15.9.2 fixes the problem. Hopefully such bug won't come back as it had reappeared a few times in last few years for different causes.
– ZZZ
Nov 23 '18 at 4:19
thanks for the update. I haven't updated to 15.9.2 yet still with 15.9. However this morning when connecting to Mac from Windows, VS 2017 updated the mono lib in xcode to the latest. Previously I had done such update to latest mono manually in Mac, however, VS reported implementable issue so I had to reverse back. Very strange. I will be checking soon and report back here.
– ZZZ
Nov 22 '18 at 2:52
thanks for the update. I haven't updated to 15.9.2 yet still with 15.9. However this morning when connecting to Mac from Windows, VS 2017 updated the mono lib in xcode to the latest. Previously I had done such update to latest mono manually in Mac, however, VS reported implementable issue so I had to reverse back. Very strange. I will be checking soon and report back here.
– ZZZ
Nov 22 '18 at 2:52
1
1
confirmed that 15.9.2 fixes the problem. Hopefully such bug won't come back as it had reappeared a few times in last few years for different causes.
– ZZZ
Nov 23 '18 at 4:19
confirmed that 15.9.2 fixes the problem. Hopefully such bug won't come back as it had reappeared a few times in last few years for different causes.
– ZZZ
Nov 23 '18 at 4:19
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53336066%2fvisual-studio-2017-v15-9-storyboard-designer-cannot-connect-to-mac-while-vs-is-c%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
My current workaround is to create a dummy project in xCode and use the storyboard editor there, and then manually copy the xml back to the Windows machine.Having to learn the strange UI of xcode, and whole process may be just slightly better than drafting xml.
– ZZZ
Nov 16 '18 at 20:06