Game doesn't run on 1st Gen Ipod touch[Unity Bug that is now Fixed]

I can’t get my game or any games for that matter, including the Unity Penelope demo to run on a 1st Generation Ipod touch. the OS that is installed is 3.1.3 and I am using Xcode 4.2

The errors I get in the debug console are:

→ applicationDidFinishLaunching() Mono path[0] =
‘/var/mobile/Applications/F675514A-89F4-4840-ADF0-75BB0B67845F/Penelope.app/Data/Managed’
2012-01-30 17:26:40.726
Penelope[201:207] *** -[UIScreen
scale]: unrecognized selector sent to
instance 0x1e0f2e0 2012-01-30
17:26:40.734 Penelope[201:207] ***
Terminating app due to uncaught
exception
‘NSInvalidArgumentException’, reason:
‘*** -[UIScreen scale]: unrecognized
selector sent to instance 0x1e0f2e0’
2012-01-30 17:26:40.746
Penelope[201:207] Stack: (…)
terminate called after throwing an
instance of ‘NSException’

and xcode points me to this code from AppController.mm

else
{
	if ([UIScreen mainScreen].scale > 1.0)
		launchImageName = @"Default@2x.png";
	else
		launchImageName = @"Default.png";
}

Help needed, thanks in advance.

Press Edit (in the top bar) > Project Settings > and click on Player. Make sure the pictures are set.

there is no scale in older SDK’s. You will have to check first if it respondsToSelector

Ok I update the xcode to this based of an searching other places on the web(i’m not much of a programmer).

else
	{
    if ([[UIScreen mainScreen] respondsToSelector:@selector(scale)]) {
        if ([UIScreen mainScreen].scale > 1.0)
			launchImageName = @"Default@2x.png";
        else
            launchImageName = @"Default.png";
    }
		else
			launchImageName = @"Default.png";
	}

It seems to get past it but, now the device crashes when the game loads, I have no errors but the following warnings in the debug console:

warning: Could not find object file “/var/tmp/AppleMBX/AppleMBX-48~174/AppleMBX.build/MBXGLEngine.build/Objects-normal/armv6/twiddle_block.o” - no debug information available for “/SourceCache/AppleMBX/AppleMBX-48/MBXGLEngine/twiddle_block.c”.

This was a bug that was FIXED in the release version of Unity 3.5 and is no longer an issue.