Bug 20512 - iOS Designer - Storyboard repeatedly 'forgets' images
Summary: iOS Designer - Storyboard repeatedly 'forgets' images
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 3.0
Hardware: PC Windows
: Normal normal
Target Milestone: 3.6
Assignee: Jose Medrano
URL:
: 24406 ()
Depends on:
Blocks:
 
Reported: 2014-06-10 09:32 UTC by F Masolijn
Modified: 2014-11-10 18:10 UTC (History)
6 users (show)

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

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 F Masolijn 2014-06-10 09:32:09 UTC
While editing a storyboard, sometimes an element (UIImageView or UIButton) 'forgets' the image it's supposed to display.
These elements don't forget their layout, just their selected image or background-image. I've had this occur both with UIImageViews and UIButtons.

So far I've not been able to consistently reproduce this. But it has happened approximately 8 times this past hour.
The selected images are add to the project as BundleResource and the resources themselves aren't disappearing. It's annoying as I keep having to reselect the proper image for some of the views in the storyboard.

Are there any logs I can check/provide to see whether something about this is logged?
Comment 1 F Masolijn 2014-06-10 09:46:29 UTC
It typically happens at the moment I add a new view element, for example a new ViewController. Still not found a sure way to duplicate this.
Comment 2 Mohit Kheterpal 2014-06-11 10:55:19 UTC
I have tried to reproduce this issue.

I have added image in ImageView but when I deploy application on mac then Image is disappear from Imageview in storyboard. However, Image is display on simulator.

Screencast : http://screencast.com/t/oIIFGQIB

IDE Logs: https://gist.github.com/Mohit-Kheterpal/9806e0f839f21601ced5

Thanks.
Comment 3 F Masolijn 2014-06-11 11:13:06 UTC
I'll check tomorrow morning whether I can also confirm the images still correctly being displayed in simulator.
Comment 4 F Masolijn 2014-06-12 04:31:35 UTC
Most consistent way I've found to reproduce this issue:

Create a decent sized storyboard (multiple Views/ViewControllers).
Have multiple UIImageViews and UIButtons in each of the Views.
Assigns png's to each of these UIImageViews and UIButtons.
Now add a single new image resource to the project.

Result: almost all UIButtons and some UIImageViews forget to render their image when the screen updates in iOS Designer. These images are then also not rendered in iOS Simulator.

When I view the code of the Storyboard it turns out that the iOS Designer stripped the code that pertains to the images it 'forgets'. So it isn't just 'not rendering'. It's actually malforming the Storyboard file when updating the Solution with new Resources.
Comment 8 Mohit Kheterpal 2014-11-07 08:16:36 UTC
I have checked this issue and this issue is working fine now i.e. storyboard is not forgetting images when we deploy application on device and simulator as shown in screencast : http://screencast.com/t/wgRgiOGkXb9a

Using XVS 3.8.113 + X.iOS 8.4.0.28

Hence closing this issue.
Comment 9 Alan McGovern 2014-11-10 18:10:55 UTC
*** Bug 24406 has been marked as a duplicate of this bug. ***