4

I've developed and application for iPhone. It works fine on os4 but it does not work on os3.1. In fact works but there are some problems; after splash screen a what screen appears. while I leaving the application I can see the application is opened successfully but just see while exiting.

So I wonder if there is a tool which says which apis have problems with os3.1? So I have a chance to replace them.

Kara
  • 6,115
  • 16
  • 50
  • 57
ysnky
  • 281
  • 4
  • 12

3 Answers3

1

Set your project's Base SDK to iphone-os-3-1, then build. All the error messages about classes, methods, and functions that don't exist must designate things added since iphone-os-3-1, since your project built and linked fine against the iphone-os-4-0 SDK.

If you don't have the iphone-os-3-1 SDK, try this instead:

  • Open your project's Build Settings.
  • Find the "Preprocessor Macros" setting.
  • Edit it and add __IPHONE_OS_VERSION_MAX_ALLOWED=30100

Now, try building. This should cause everything introduced after iOS 3.1 to be labeled unavailable, producing the same errors as if you had switched to the iphone-os-3-1 SDK.

Jeremy W. Sherman
  • 35,901
  • 5
  • 77
  • 111
  • but there are only 4.0 and 3.2. as base sdk. – ysnky Dec 07 '10 at 21:29
  • it gives 8 errors but not make sense for me /UIView.h:250: error: expected ')' before 'UIViewAnimationOptions' /UIDevice.h:76: error: expected specifier-qualifier-list before 'UIUserInterfaceIdiom' /UIApplication.h:187: error: expected specifier-qualifier-list before 'UIApplicationState' /UIApplication.h:190: error: expected ')' before 'UIBackgroundTaskIdentifier' – ysnky Dec 07 '10 at 22:18
  • Sure enough, docs show that all those things were introduced after 3.1.3. If you have to support 3.1.3 then you have to work around them. – Adam Eberbach Dec 07 '10 at 22:56
  • Start by focusing on what you can understand. The low-hanging fruit are the names after the "before" – `UIViewAnimationOptions`, `UIUserInterfaceIdiom`, `UIApplicationState`, `UIBackgroundTaskIdentifier`. If you look those up, you will most likely find that these are names introduced after the 3.1 SDK. – Jeremy W. Sherman Dec 08 '10 at 00:35
1

If you want to check a specific API, just run this in your code somewhere with an appropriate response. For example, to see if print is supported, run this...

if (NSClassFromString(@"UIPrintInfo")) {

}
sudo rm -rf
  • 29,408
  • 19
  • 102
  • 161
0

It's a good idea to get a second installation of Xcode for this situation, in this case you need 3.2.1 with SDK 3.1.3 - I wish I could help you with a download link since it is no longer shown on Apple's page, but I have googled in the past and found direct, official download links which will work as long as you are signed in with your developer account, so good luck.

The annoying bit is that you need to go through your project files and set "Base SDK" to 3.1.3 and then back once you have completed the exercise. But it is the easiest way to flag what you can't do in 3.1.3. "sudo rm -rf" (I feel nervous even typing that) has an excellent method there but you need to have an inkling of what might be safe and what might not before you implement it or else you end up with code 10x the size it needs to be.

Apple really needs to sort out this issue - hopefully by flagging methods that are prior to your specified "Deployment Target", in the same way that deprecated methods are flagged.

Adam Eberbach
  • 12,309
  • 6
  • 62
  • 114