Does the deployment task do more than control compiler warnings?

Question

I recently introduced an update for an application using a deployment target of 3.2 (it was 3.0 in my debug settings, but I must have not noticed the distribution settings). But in the application setup in iTunes Connect, I indicated that the minimum supported OS version is 3.0. Now I get reports from users in OS 3.1 that the application will not work.

I created new binaries with a fixed deployment target, but I have no way to test it. I do not have devices running the OS. 3.2, and the simulator will not fall below 3.2 (why not ?!). I would really like to present this as a correction, only so that it still does not work ...

So setting a deployment target is more than just controlling compiler warnings (for example, if I used an API that is only available in the new SDK)? As far as I know, I do not use any APIs that were not available in OS 3.0 (there are also no warnings).

Answer 1

If someone iOS has an earlier version than the deployment target, the application will refuse to run.

- , 3.1. 4.0. iOS 3.1 . , 3.1. .

, . - , , , , , .

.