[...]The Air Source » Blog Archive » Memory usage in UIImagePickerController[...]…

Thank you for submitting ###### to the App Store. Unfortunately it cannot be added to the App Store because it is modifying or extending an undocumented API, which as outlined in the iPhone SDK Agreement section 3.3.1 is prohibited:

“3.3.1 Applications may only use Published APIs in the manner prescribed by Apple and must not use or call any unpublished or private APIs. ”

There is no documentation for the custom subclasses or self-contained views of UIImagePickerController – this includes PLCameraView nor it’s custom subclasses (PLImageTile, PLRotationView, PLImageScroller, PLImageView, PLCropOverlay, PLCropLCDLayer, TPBottomDualButtonBar, TPPushButton and TPCameraPushButton) – in the iPhone SDK.

I’m keeping the same UIImagePickerController around and reusing it like suggested. I’m also compiling against 2.2 and 2.2.1, and still no luck. If I don’t keep the camera picker around, my app usually crashes after the first or second picture. I’ve even tried scaling the picture to half the size before saving it to conserve memory.

My first version of the app was rejected by Apple because I used one undocumented API to get around the memory issue. Now that I’ve rewritten it using the “stock” camera control I can’t get around this memory bug.

I’m willing to give someone access to the full code base of my application if they think they can help. Is it even worth finishing a camera application since 3.0 deprecates the method needed to get the image from the camera anyway?