35

[!] Unable to satisfy the following requirements:

  • Google/SignIn required by Podfile
  • Google/SignIn required by Podfile
  • Google/SignIn required by Podfile
  • Google/SignIn required by Podfile
  • Google/SignIn (= 1.3.2) required by Podfile.lock

Specs satisfying the Google/SignIn dependency were found, but they required a higher minimum deployment target.

Specs satisfying the Google/SignIn dependency were found, but they required a higher minimum deployment target.

Specs satisfying the Google/SignIn dependency were found, but they required a higher minimum deployment target.

Specs satisfying the Google/SignIn dependency were found, but they required a higher minimum deployment target.

Specs satisfying the Google/SignIn (= 1.3.2) dependency were found, but they required a higher minimum deployment target.

Skander Fathallah
  • 503
  • 1
  • 5
  • 10

10 Answers10

67

Your deployment target has to be moved up to the highest minimum target required by any dependency. enter image description here Also, make sure the global platform in your Podfile matches the highest minimum target required by any dependency.

Ashildr
  • 1,783
  • 3
  • 16
  • 25
6

Cocoapods error

you get next error:

dependency were found, but they required a higher minimum deployment target

When .podfile

platform :ios, '<version>'

is not equal to .podspec

<variable>.platform = :ios, "<version>"

[Local CocoaPod]

yoAlex5
  • 29,217
  • 8
  • 193
  • 205
  • 1
    This is what I needed to find the minimum deployment target required by the offending plugin. The console output specifies the offending plugin (in OPs case, `Google/SignIn`) but does not specify the minimum deployment version number the plugin requires. Thanks! – troyshu Aug 19 '21 at 14:18
  • 1
    In a Flutter iOS project, the required platform details can be found in the following location: `ios/Pods/Local Podspecs/.json` which may include `"platforms": { "ios": "13.0" }` or similar in it. Your project would need to target the maximum necessary among all your used packages. This info is often also included in each package's release notes. – Tommy Elliott Aug 11 '22 at 19:05
3

I went to my Podfile and changed my deployment target to the highest one that was in my Pods/Local Podspecs

Ryker
  • 446
  • 3
  • 14
2

I solved the problem. I selected my project at the top of my project navigator -> General -> Deployment info -> Deployment Target -> (Set the the most current)

1

It's pretty self-explanatory. Your deployment target has to be moved up to the highest minimum target required by any dependency. Check what iOS version Google/SignIn requires. If this checks out, make sure all your deployment targets set a satisfactory minimum target version.

diatrevolo
  • 2,782
  • 26
  • 45
1

i solved it by removing my Google/SignIn version and installing again my pods.

Skander Fathallah
  • 503
  • 1
  • 5
  • 10
1

I solved via:

pod 'Alamofire', '~4.0'

To

pod 'Alamofire'
Relay Just
  • 15
  • 2
Winner
  • 45
  • 1
  • 4
  • 16
1

For me, my minimum target is already high enough. I need a pod update ThePackageName (WARN: this will change the version you are using). See https://github.com/CocoaPods/CocoaPods/issues/4373 for more details.

ch271828n
  • 15,854
  • 5
  • 53
  • 88
0

I think Google/SignIn SDK supports iOS7 or later. Try a higher minimum deployment target.

Pankaj
  • 397
  • 1
  • 3
  • 13
0

What solved it for me was

pod repo update

as the error details suggested

ΞΫΛL
  • 184
  • 7