Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: MacOS Remote USB - please bring it back. #5442

Open
tlhintoq opened this Issue Jan 18, 2019 · 3 comments

Comments

Projects
None yet
3 participants
@tlhintoq
Copy link

tlhintoq commented Jan 18, 2019

###Request###
Please re-active the MacOS remote debugging feature from 2016. It worked great then just disappeared without a final release.

This feature got a standing ovation at Evolve 2016. It was around for about a week, then pulled.
There was a survey on Twitter that MANY people didn't know about. Then ... well .... hello ... nothing.

The thread for it on Xamarin Forums still has people wanting to know when this will be available again.
https://forums.xamarin.com/discussion/comment/311153#Comment_311153

Please bring this back - when it was there it worked great.

Steps to Reproduce

  1. Nothing to reproduce

Expected Behavior

To remotely use an iOS device connected to the Windows PC, as if it were connected directly to the Macintosh build host that is commonly in a rack someplace other than the developer desk.

Actual Behavior

Worked great at Evolve 2016 - then disappeared.

Environment

Windows has the iOS device connected by USB.
Mac sees the device as if it were connected directly to the mac.

Build Logs

Nothing to log

Example Project (If Possible)

No example required

Related to #1360 where it was simply closed as 'wrong area' but the closer didn't mention what would be the right area. @johnhair suggested the iOS area.

VS bug #772684

@spouliot spouliot added this to the Future milestone Jan 18, 2019

@xamarin-release-manager xamarin-release-manager removed this from the Future milestone Jan 18, 2019

@spouliot

This comment has been minimized.

Copy link
Contributor

spouliot commented Jan 18, 2019

@tlhintoq GitHub issues are meant for the open sourced SDK [1]. The best place for IDE (or non-open source) feature requests is Visual Studio Community https://developercommunity.visualstudio.com/spaces/8/index.html

[1] we can sync the issue to our internal bug tracker so the XVS (Windows side team will see the issue) but that does not have the exact same visibility.

@spouliot spouliot added this to the Future milestone Jan 18, 2019

@tlhintoq

This comment has been minimized.

Copy link
Author

tlhintoq commented Jan 18, 2019

Thanks for the response. What do you think is the best thing to do with the request so it gets the right visibility from the team and maybe some love with respect to it being worked on?

@spouliot

This comment has been minimized.

Copy link
Contributor

spouliot commented Jan 21, 2019

@tlhintoq in both cases (here or Visual Studio Community) there will be an internal issue created, so "team wise" it's identical (same end result).

You might get more external visibility (e.g. more community comments) in Visual Studio Community since this is where the IDE (both Windows and Mac) redirect their users for feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.