iOS Build Error 'Cannot find type 'GIDSignInDelegate' in scope' in PRO template v4.0.0

[JanPhill]

Hi,

I am getting the Swift Compiler Error 'Cannot find type 'GIDSignInDelegate' when trying to build the Ionic Full Starter App v4.0.0 (PRO version) in Xcode.

I made sure the GoogleService-Info.plist file is present in the app folder as explained in the docs. I also followed #31 but without success.

In Ionic Full Starter App v3.0.0 I had the same error but was able to fix it by upgrading to capacitor-firebase-auth@3.1.2-rc.3 but in v4.0.0 this is not possible anymore as rxjs was upgraded to 7.4.0 and capacitor-firebase-auth@3.1.2-rc.3 requires a peer of rxjs@~6.6.7 and results in angular build errors when using rxjs@7.4.0.

Would be very grateful for advice.

Best,
Jan

[djabif]

Hey Jan, which steps did you follow? I've just built everything from scratch and didn't have any problem. You could try downgrading rxjs if you need.

[JanPhill]

Hi Dayana,

I followed the steps in your documentation https://ionic-5-full-starter-app-docs.ionicthemes.com/capacitor to deploy the app to an ios device using capacitor.

This is the error I get in Xcode when I try to build the untouched app from your repository:

Even tried to completely remove and readd the ios platform but without success. Meanwhile I got it working by upgrading capacitor-firebase-auth to v3.1.2-rc.3 and downgrading rxjs to v6.6.7.

Which version of Xcode are you using?

Best,
Jan

[djabif]

Hey Jan, thanks for the update and for the information.

I'm using Xcode Version 12.5.1 (12E507).
I recorded a video showing how to run the ionic template in iOS and Android. Maybe it helps.
There's no need to remove and re-add the platforms.

I'm using capacitor-firebase-auth v3.0.0 and rxjs 7.4.0

As soon as the capacitor-firebase-auth gets updated to the latest version of Firebase we will update the template.

[JanPhill]

Hi Dayana,

thank you very much for the video. I followed the steps but still getting the build error.

I am using the most recent version of Xcode 13.2.1. Maybe you could update to that version and see if that reproduces the error on your side.

Best,
Jan