error: module file's minimum deployment target is ios8.3 v8.3
Solution 1
You might have created a target after updating Xcode, which made 8.3 the iOS Deployment Target in Build Settings for that target.
I fixed this by:
- Setting the iOS Deployment Target to 8.0 (Which is the same as the rest of the project)
Note iOS version mismatch in this screenshot (one is 10.0, other is 9.3)
- Doing a clean (Command+Shift+k) and build
If a clean+build doesn't fix it, switching the device/simulator that you are deploying to from the scheme menu and building again should help.
Solution 2
This error might also crop up if you're unit testing. So in addition to what @Tony and @Allreadyhome has suggested, do the following:
- With your test target selected, go to 'Build Settings'
- Search for 'iOS Deployment target' at the top search bar.
- Change the value for the iOS Deployment Target accordingly, (in the context of this question, you will change the deployment target to 8.0)
And you should be good.
Solution 3
As mentioned by Tony you have to
1. Set the iOS Deployment Target to 8.0
If using Pods the further step you may need to do:
2. Go into the Pods dependancies and change the deployment targets to 8.0 also.
In my case, I had to change the deployment target on each of my pods to 8.0 as they were all on 8.3.
Solution 4
In your Pod File, just delete the comment at this line:
platform :ios, '8.0'
It work for me.
Solution 5
I've encountered error:
Module file's minimum deployment target is ios9.2 v9.2
After I changed the iOS deployment target to 8.0 for my PROJECT. The project is created by Xcode 7.2, with 'Include Unit Tests' and 'Include UI Tests' checked.
Because of the XCUIApplication() requires iOS 9.0+, to fix the error, just change the deployment target of UI Tests to 9.0 or above, and leaves 8.0 for other targets.
Related videos on Youtube
Vatsal Manot
Updated on July 08, 2022Comments
-
Vatsal Manot almost 2 years
All attempts to import a dynamic framework in an Xcode playground yield the following error:
error: module file's minimum deployment target is ios8.3 v8.3
-
Vatsal Manot almost 9 yearsJust a note: this issue has been resolved with the GM build of Xcode 6.3.
-
Nate Uni almost 9 yearsNot for me .. just got the build and the issue is still applicable for me.
-
Suz almost 9 yearsI had to try multiple times: When I changed the deployment target, it didn't seem to actually change until I switched to a different deployment device. Then it finally worked.
-
King-Wizard almost 9 yearsChanging the deployment target of my Xcode project fixed the problem for me.
-
William Entriken about 8 yearsSame problem Version 7.2.1 (7C1002)
-
jotaEsse almost 8 yearsI've been looking for a way to do this for weeks! Thanks a lot! Just a hint, maybe it won't show up if the tab "Basic" is selected. Choose "All" before searching and you'll be good to go.
-
Yevhen Dubinin over 7 yearsI wonder, how dynamic framework and the app would behave during runtime on iOS 8, if the app deployment target is set to iOS 8.0 and the framework's is iOS 9.0. ?
-
Vatsal Manot over 7 years@EugeneDubinin: It would crash upon usage of non-existent APIs. Developers attempting to support multiple iOS versions usually implement runtime checks for these sort of things.
-
Jacob F. Davis C-CISO over 6 yearsFor case: "Module file's minimum deployment target is ios10.0 v10.0", My target was already 10.0. I cleaned and rebuilt: no joy I changed deployment target, cleaned rebuild: no joy I changed target to 10.1, clean rebuild, change back to 10.0, clean rebuild: no joy. Could not resolve issue with this solution.
-
Jacob F. Davis C-CISO over 6 yearsThis answer explained in a different way led me to the answer: stackoverflow.com/questions/32692828/… I edited this answer by adding screenshots to show exactly where to change the iOS version data.
-
Michael almost 6 yearsGot this error in xCode 9.4 with iOS 11.4 while working through Ray Wenderlich's Framework Tutorial (raywenderlich.com/126365/ios-frameworks-tutorial) . There was an old IOS 8.0 target buried deep in the test suite settings structure that @JacobDavis 's post help me find.
-
u2Fan over 5 yearsThis also led me to check the "Project"s build settings, and they were old, too. Updated those, and now I'm golden! Thanks!
-
David J about 5 yearsYou're a life saver. I would have never figured this out.
-
gnarlybracket about 4 years"With your test target selected..." was what I was missing from other answers.