GoogleSignIn required to be signed in Xcode about googlesignin-ios HOT 15 OPEN

+1
Same problem.

from googlesignin-ios.

Installing CocoaPods 1.12.0 resolved this issue for us.

from googlesignin-ios.

I faced this problem on Xcode 14.0 too.
I temporary solved it by disabling Code signing for Pod by adding these lines to bottom of Podfile

post_install do |installer|
  installer.generated_projects.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
        config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
        config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = ""
      end
    end
end

from googlesignin-ios.

+1, same on xcode 14.0

from googlesignin-ios.

@jkichline can you tell me how and at what point you're experiencing this requirement?

from googlesignin-ios.

Here's a screenshot. You'll see that GoogleSignIn in the middle column is a different color than the other frameworks and requires it to be signed in order to submit it to the App Store. the other frameworks don't need this and can go unsigned. I need to go through and manually sign the frameworks and make sure I pick the correct options for iOS vs Mac Catalyst for each of my builds (debug, beta, release, distribution). While it wouldn't be too bad if I did this once, every time I "pod update", this information is lost and needs to be entered over and over again, and I need to run "pod update" every time I switch between branches in our code base which means I run the risk of having a failed upload to the App Store every time.

Here is the warning/error we get from the App Store for the Mac Catalyst version if we don't get the settings correct. This means we need to submit another build.

I guess I wonder why GoogleSignIn is any different from any other frameworks?

from googlesignin-ios.

xcode 14.0 beta has this problem.

from googlesignin-ios.

+1, same on xcode 14 beta 3

from googlesignin-ios.

@petea any plans here? Would be good to have this fixed unless this is some actual xcode 14 bug that Apple needs to resolve - I haven't investigated this, but it would be good to have this sorted out

from googlesignin-ios.

Related discussion and possible workaround at firebase/firebase-ios-sdk#9886

from googlesignin-ios.

+1

from googlesignin-ios.

Probably related to #226 and #223

from googlesignin-ios.

I faced this problem on Xcode 14.0 too. I temporary solved it by disabling Code signing for Pod by adding these lines to bottom of Podfile

post_install do |installer|
  installer.generated_projects.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
        config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
        config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = ""
      end
    end
end

On my side, this kind of fixed the issue.

Kind of because I have an app that contains an internal pod (via podspec) that contains GoogleSignIn and the solution only fixed the issue on the internal pod. Supposedly I would have to include this post_install statement on the internal pod's podspec but I think this is not possible. Any idea on how to overcome this?

from googlesignin-ios.

/Users/romas/Documents/unity/xcode/yacht/Pods/Pods.xcodeproj Signing for "GoogleSignIn-GoogleSignIn" requires a development team. Select a development team in the Signing & Capabilities editor.

I can manually specify the Team ID in XCode. But it's not right for me. How can I do this automatically from Unity?

from googlesignin-ios.

Workaround fix from Unity. I added these lines to the end of the podfile in OnPostprocessBuild() method:

plugin 'cocoapods-pod-sign'
skip_pod_bundle_sign

Also I ran the command on the Mac:
$ gem install cocoapods-pod-sign

from googlesignin-ios.