ansaurus

Question

Apple rejected me, no idea why, or how to fix it.

Answer 1

+3 A:

Your app used too much memory. Check your app with Instruments (Object Allocations or Leaks) and see if you can reduce memory allocation.

KennyTM 2010-01-16 05:20:50

what are good ways to reduce memory allocations? and is it best to let the system manage it (NSString *string = @"hello";) or do it yourself like (NSString *string = [[NSString alloc] init];)

Sam Jarman 2010-01-16 05:41:51

For strings, `NSString* const string = @"hello";` if possible. If you do it yourself remember to `-release` it.

KennyTM 2010-01-16 05:45:58

Answer 2

+2 A:

You app is using way, way too much memory. It'll never run on older devices with 128 MB of RAM.

Darren 2010-01-16 05:21:38

can you just specify that you need a newer device to run it? they are only going to get faster and faster.

Sam Jarman 2010-01-16 05:42:26

Do you really want to drop 10-20 million people out of the running to buy your application when you could just spend some time optimizing and make it work for everyone? For a game I could MAYBE see this argument if you were wanting to use only the latest OpenGL features.

Kendall Helmstetter Gelner 2010-01-16 05:59:58

nah.. i'll try optimizing it.

Sam Jarman 2010-01-16 06:01:53

To put it in perspective: with Safari, Mail, and iPod running in the background, a typical app can start triggering low-memory conditions at 1800 pages (in my experience). Your app is using almost 6000 pages before it's even off the ground. There's aren't minor leaks we're talking about; your app is doing something seriously wrong. The good news is that such egregious memory usage should be very easy to fix, once you figure out what the problem is.

Darren 2010-01-16 06:02:46

@Darren. you think with something this wrong, there would some warnings or errors or something like that..

Sam Jarman 2010-01-16 06:51:00

There are, the app is given a didReceiveMemoryWarning notification when memory is getting really tight. Your app should react to that and try and free up memory wherever it can. But if you use up memory fast enough, the app may not even get that and just be shut down.

Kendall Helmstetter Gelner 2010-01-16 07:21:38

Answer 3

+4 A:

See "free pages: 309"? not good, means you are using a bunch of memory then when it is all used it crashes. And the purgeable pages = 0 is memory that can't be reclaimed so it's a memory issue.

Do a "Build and Analyze" and run "Leaks" to find memory leaks and places you can run more efficiently.

ACBurk 2010-01-16 05:26:42

I have no leaks though. ALl memory seems to be /accounted/ for.

Sam Jarman 2010-01-16 05:47:42

Answer 4

+3 A:

Your iPhone 3GS and the Simulator have far more memory than the other iPhone OS devices. To work on all devices, you should use no more than 20 MB of memory.

CajunLuke 2010-01-16 05:43:56

how do you tell if how much its using now?

Sam Jarman 2010-01-16 05:47:11

Have you tried running your apps in Instruments (Run -> Run with Performance tools...)

KennyTM 2010-01-16 06:08:56

yes i have. and thinks look ok to me. (although, that is not saying much whatsoever)

Sam Jarman 2010-01-16 07:03:57

Answer 5

+3 A:

As others have said, you are using too much memory.

If you are using multiple pages of view controllers, try this simple test - run your app with the ObjectAlloc Instrument. Click on something to bring up a subview, you should see your memory increase - now dismiss that view and go back to the main one, the memory should go down. If it does not, that is your problem (or one of them anyway, but that is a likley starting point).

To try and track this down, place breakpoints in dealloc for each of your view controllers and see what actually gets called. For view controllers that are not released like you expect, in ObjectAlloc you can see where each retain against an object was issued, and decide what retained the object when it should not have done so.

In general the ObjectAlloc flow should look like a graph that goes up and down all the time, not constantly rising.

Also if you are using a lot of images consider re-sizing them to the exact size you need instead of starting with a much larger size and scaling. Using that much memory must be due to using images and not releasing them. Leaks will not report anything if you still have references to memory you are retaining.

Also, buy an older Touch for testing.

Kendall Helmstetter Gelner 2010-01-16 05:55:21

"Also if you are using a lot of images consider re-sizing them to the exact size you need instead of starting with a much larger size and scaling."i think that could be the problem.. read the comment on the question i just wrote.

Sam Jarman 2010-01-16 06:02:49

I commented on that. There's really no reason you should have to have them all loaded though, you really should change it to load only images as you need them, and get rid on ones you are not using.

Kendall Helmstetter Gelner 2010-01-16 06:11:43

OK. I JUST RAN THEM ALL THROUGH PHOTOSHOP, AND BROUGHT THE ALLOCATION TOTAL BACK DOWN TO AN ACCEPTABLE LEVEL. THANKS KENDALL.

Sam Jarman 2010-01-16 09:21:52

I'd still recommend getting a Touch to try it out on... though I'll bet that helped a lot. I'm glad that seemed to be the main problem.

Kendall Helmstetter Gelner 2010-01-16 19:59:14

ansaurus

tags:

views:

answers:

Apple rejected me, no idea why, or how to fix it.

related questions