Finding iOS 4 to iOS 5 app incompatibility problem

[Joseph Nardone]

I work for an ad agency that had an app written for a client by a contractor before I arrived. The app was developed for iOS 4 and works fine on iOS 4 but the app malfunctions (but does not crash) on iOS 5. There are no warnings in the code.

I have been asked to analyze the code to figure out what might be wrong.

This app was for enterprise deployment so there may be undocumented methods used.

Is there a way that I can easily scan the code (like the app store does) for illegal/deprecated methods that might be causing the problems?

The project folder contains over 1000 files!

Thanks

[BrianSlick]

Unless there is some secret switch for doing enterprise development, then undocumented code is simply methods that do not appear in header files. So cleaning the project and inspecting all warnings should reveal most of them. That most likely won't catch any performSelector calls, but those won't take long to inspect.

Is it over 1000 files because the app is just that complex, or was the contractor not a very good developer?

What kinds of malfunctions? There are differences in iOS 5 that can result in undesired behaviors.

[Joseph Nardone]

Thanks.

I got rid of all the warnings already. I think what I need is a list if changes from iOS 4 to iOS 5 that would not give warnings but change behavior.

An example would be the parentViewController/presentingViewController change from iOS 4 to iOS 5 which changed a lot of the apps that we had developed but does not give warnings.

The code in question was started by a freelancer, handed off to another freelancer, then to a large development company to finish in a hurry.