At the moment you have to specify the names using the CFBundleIconFiles

Multi-tasking can be great, but it has added some complexity to programming on the iPhone. For many apps there really is no advantage. For instance, does the “That’s What She Said” button really need to stay in memory?

It’s some added complexity that programmers don’t need.. some of the more complex memory intensive apps will just exit anyways, and programming the app to suspend can be a highly complicated task.

Fortunately there is a simple way to make your iOS 4 apps terminate for real when the user taps the home button.

This is a simple process:

Open your info.plist file
Add The Key UIApplicationExitsOnSuspend
Set the new key to YES
Now your applicationwillterminate: method will be run when the user taps the home key, and your app will exit for real.

Get EXEC_BAD_ACCESS when hiding a bottom bar that doesn’t exist

Steps to Reproduce:

SettingsViewController* settings = [[SettingsViewController alloc] init];
[settings setHidesBottomBarWhenPushed:YES];
[self.navigationController pushViewController:settings animated:YES];

[settings release];

The active view doesn’t have a bottom bar

Expected Results:
When the view is popped it should ignore the fact that there was no bottom bar

Actual Results:
get an exec_bad_access

Regression:

Notes:
removing the line that setHidesBottomBarWhenPushed, corrects the issue.

Obviously this is redundant code and I shouldn’t be calling it (I’ve now removed it), but I would of thought he SDK would check before trying to restore a non existent bottombar

Upload image to simulator

Clicking save will then include your image.

Apple act as an undisclosed agent. You supply your products to Apple (one supply line), who then market and supply them to consumers (another supply line). Apple charge VAT on their supply line, as you’d expect.

Apple’s commission is a markup in the price, which they then add VAT to. This is very important. At no point do Apple invoice you for commission. Because of this, under HMRC rules this isn’t deemed to be a supply of “agency services” from Apple to you (the agency services in question being the marketing and sale of Apps on iTunes). That’s the second supply line – Apple to the Consumer. You can then account for VAT on your supply to Apple as normal. Because you are supplying software to Apple’s EU subsidiary, HMRC’s place of supply regulations mean you’re outside the scope for VAT.

So:

You sell an app for £0.99 (it’s an easy number to use in this example, for simplicity)
Apple charges the user £0.84 (plus VAT)
Apple takes their commission (£0.25), except it’s technically a mark-up on price, not commission.
This leaves £0.59, which is the cost of supply. This is what you would invoice Apple for (even if you’re only generating invoices for your own internal paperwork)
As you supplied your product to Apple for £0.59, who then sold it on at a markup to the public, you were supplying directly to a business, and thus outside the scope of VAT.

Fortunately, the contract you have isn’t with Apple UK, but Apple Sàrl, based in Luxumberg. When a seller in one EU member state invoices a company in a different EU member state they can zero rate the VAT. You should still put VAT as an item on your invoices, but rate it at zero (ie, £0.00). As long as you use the addresses below on your invoices, HMRC should be satisfied.

Really Important point: Because your iTunes income is coming from another member state, you need to declare it in Box 8 of your VAT return. If you have an accountant you don’t need to worry about this, you just need to make sure s/he is aware your App income is from within the EU but outside the UK.

Should you need an address and Luxumberg VAT number for your records, it’s as follows:

Billing Address:
iTunes s.à r. l.
8 rue Heinrich Heine
L-1720 Luxembourg
TVA/VAT No.: LU20165772

Invoicing Address:
App Store Invoicing
Apple Operations Europe
iTunes s.à r. l.
Hollyhill Industrial Estate
Hollyhill
Cork Ireland

	NSString *email = [newEmailAddress.text lowercaseString];
	NSString *emailRegEx =
    @"(?:[a-z0-9!#$%\\&'*+/=?\\^_`{|}~-]+(?:\\.[a-z0-9!#$%\\&'*+/=?\\^_`{|}"
    @"~-]+)*|\"(?:[\\x01-\\x08\\x0b\\x0c\\x0e-\\x1f\\x21\\x23-\\x5b\\x5d-\\"
    @"x7f]|\\\\[\\x01-\\x09\\x0b\\x0c\\x0e-\\x7f])*\")@(?:(?:[a-z0-9](?:[a-"
    @"z0-9-]*[a-z0-9])?\\.)+[a-z0-9](?:[a-z0-9-]*[a-z0-9])?|\\[(?:(?:25[0-5"
    @"]|2[0-4][0-9]|[01]?[0-9][0-9]?)\\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-"
    @"9][0-9]?|[a-z0-9-]*[a-z0-9]:(?:[\\x01-\\x08\\x0b\\x0c\\x0e-\\x1f\\x21"
    @"-\\x5a\\x53-\\x7f]|\\\\[\\x01-\\x09\\x0b\\x0c\\x0e-\\x7f])+)\\])";

	NSPredicate *regExPredicate =[NSPredicate predicateWithFormat:@"SELF MATCHES %@", emailRegEx];
	BOOL myStringMatchesRegEx = [regExPredicate evaluateWithObject:email];
	if(!myStringMatchesRegEx){
		UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@"Correct Email" message:@"Please enter a valid email address" delegate:nil cancelButtonTitle:@"OK" otherButtonTitles:nil];
		[alert show];
		[alert release];
	}

The code is based on this article which describes this in a lot more detail.

	switch (row) {
		case 0:
			int i;
			i = row + 10;
			NSLog(@"%d",i);
			break;
		default:
			break;
	}

You’ll get a compile error, “Expected expression before ‘int’”. If you need to declare a variable enclose the code in curly braces and the error goes away….

	switch (row) {
		case 0:
		{
			int i;
			i = row + 10;
			NSLog(@"%d",i);
			break;
		}
		default:
			break;
	}

Note that the error only occurs if the variable declaration is the first statement in the code block.