UIImageView shows in simulator, does not show on device

[hermonir]

Hello,

I have a UIScrollView that has three view controllers added to it, as such:

	[scrollView addSubview:islandViewController.view];

On one of them, I'm adding three images in viewDidLoad:

- (void)viewDidLoad {
    [super viewDidLoad];
	
	CGRect myImageRect = CGRectMake(0.0f,0.0f, 320.0f, 480.0f);
	UIImageView *sky = [[UIImageView alloc] initWithFrame:myImageRect];
	[sky setImage:[UIImage imageNamed:@"sky.png"]];
	sky.opaque = YES; // explicitly opaque for performance
	[self.view addSubview:sky];
	[sky release];
	
	CGRect myImageRect3 = CGRectMake(0.0f,432.0f, 320.0f, 48.0f);
	UIImageView *sea = [[UIImageView alloc] initWithFrame:myImageRect3];
	[sea setImage:[UIImage imageNamed:@"sea.png"]];
	sea.opaque = NO; 
	[self.view addSubview:sea];
	[sea release];
	
	CGRect myImageRect2 = CGRectMake(40.0f,365.0f, 241.0f, 101.0f);
	UIImageView *island = [[UIImageView alloc] initWithFrame:myImageRect2];
	[island setImage:[UIImage imageNamed:@"island.png"]];
	island.opaque = NO; 
	[self.view addSubview:island];
	[island release];

}

When I'm running it on the simulator all images are shown fine. When building and running on the device, only the "sea" image is shown.

I've tried cleaning and re-building, changing the order of the images, looking for lowercase/uppercase issues... All seems fine.
What could be the problem, and more importantly, how could this be fixed?

Thanx in advance,
Nir.

[smithdale87]

When I've had problems like this, that were not related to spelling/capitalization, it's usually due to a corrupt image. I just open the .png in a graphics editor and resave it as the same name. Sometimes I guess the png gets corrupted where the simulator can still read it, but not the device.

[hermonir]

Originally Posted by smithdale87

When I've had problems like this, that were not related to spelling/capitalization, it's usually due to a corrupt image. I just open the .png in a graphics editor and resave it as the same name. Sometimes I guess the png gets corrupted where the simulator can still read it, but not the device.

Maybe I should try with jpegs, just to see what happens.

[Cori]

Got the same frustrating issue -got 3 PNGs on UIImage, shows on simulator, but not on device. And it used to show on the device, modified the code, reinstalled on the device and it stopped showing.

The thing that's weird, I copied this program to Prog B, copied the same 3 PNGs and given different names, plus 2 more PNGs for Prog B. On the simulator, Prog A and Prog B PNGs show up, but on the device, only Prog B images, not Prog A!! Take note, I use the same UIViewController: Prog A and Prog B calls the same UIViewController, the only thing different is Prog A and Prog B pass a different filename prefix to the controller. I'm so stumped!!

[baja_yu]

Are the filenames correct? And keep in mind the filesystem on device is case sensitive. "Test.png" and "test.png" would be two different files on a device.

[Cori]

You're right baja_yu - it's filename but stupid me, it's the file prefix I passed! I missed 1 letter: UguidePage - g should have been a CAP. That's why it's a consistent bug!! Duh!!

[xjulianx]

Originally Posted by baja_yu

Are the filenames correct? And keep in mind the filesystem on device is case sensitive. "Test.png" and "test.png" would be two different files on a device.

a millions thanks, u saved my life!

[jrt01uk]

I just encountered a very similar problem; thought I'd share to save someone else wasting an hour like I just did trying to solve the problem!

image@2X.png is NOT the same as image@2x.png

[Duncan C]

Originally Posted by jrt01uk

I just encountered a very similar problem; thought I'd share to save someone else wasting an hour like I just did trying to solve the problem!

image@2X.png is NOT the same as image@2x.png

I wonder how many thousands of programmer-hours us iOS developers have wasted because of the case-sensitivity of the iOS file system. I would cheerfully strangle the developer at Apple that decided to make the case sensitivity of iOS different from Mac OS (and thus different from the simulator.) I personally think case sensitive filenames are a very, very bad idea.

My other pet peeve is the screwed up coordinate system in the graphics engine in iOS. Mac OS consistently places 0,0 at the lower left, increasing as you to go up and to the right.

iOS is MOSTLY upside-down from that, but it isn't even consistent with itself!!! UIKit objects place 0,0 at the top left, and CALayers place it at the bottom left! WTF?!? Again, the programmers responsible should be shot. (this is, of course, hyperbole. I'm not really advocating violence, just expressing frustration.)