Bug 49982 - [props] Unable to view WatchOS iOS Extension page in project properties
Summary: [props] Unable to view WatchOS iOS Extension page in project properties
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.2.0 (C8)
Hardware: PC Windows
: --- normal
Target Milestone: 15.2
Assignee: Emanuel
URL:
Depends on:
Blocks:
 
Reported: 2016-12-13 22:57 UTC by Ben Beckley
Modified: 2017-04-26 12:54 UTC (History)
5 users (show)

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


Attachments
IDE logs and Screencast (1.59 MB, application/zip)
2017-04-26 12:54 UTC, Neha Kharbade
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:
VERIFIED FIXED

Description Ben Beckley 2016-12-13 22:57:06 UTC
I was opening WatchOS project properties windows using the 'alt+enter' hotkey combination and saw that the WatchOS deployment targets (1.0-3.1) were instead using iOS deployment target values (6.0-10.2). Knowing that wasn't right, I tried to reproduce it by opening and closing the project properties repeatedly. Eventually my WatchOS extension project properties' "iOS Extension" tab wouldn't render.

http://screencast.com/t/H83Yifwt6Chi

I do not have a 100% understanding on the reproduction steps, or how I triggered this behavior. But I am filing it now and will continue further investigation.

env info: https://gist.github.com/BenBeckley/f29ce024ca2d76a01a6801fcacf6864e
Comment 1 Ben Beckley 2016-12-13 23:03:49 UTC
Closed the solution, and reopened it. Upon the initial viewing of the "iOS Extension" tab, it tells me that the component cache is out of date.
http://screencast.com/t/T6V9iSrtEO

I closed and relaunched VS, and it did the "Scanning MEF Cache..." sequence. Upon reopening my project, I could view the "iOS Extension" page.
Comment 2 Jose Gallardo 2016-12-20 16:24:15 UTC
Was this just a side effect of a broken MEF Cache?

Ben, can you please let us know if you can reproduce in a different way?

Thanks!
Comment 3 Adrian Alonso 2016-12-22 17:23:40 UTC
This should be tackled as part of the props migration work
Comment 4 Adrian Alonso 2016-12-22 17:23:45 UTC
This should be tackled as part of the props migration work
Comment 5 Jose Gallardo 2017-04-12 14:40:31 UTC
Fixed on XVS 4.5.0.341
Comment 6 Neha Kharbade 2017-04-26 12:54:24 UTC
## Verified on : https://gist.github.com/nehaKh/00c1fec4c2355ccff0b1a572000b3403

## Screencast : https://www.screencast.com/t/TbwC8XmKVvyy

## Attached Ide logs and Screencast
Comment 7 Neha Kharbade 2017-04-26 12:54:43 UTC
Created attachment 21803 [details]
IDE logs and Screencast