IOS build suddenly fails after IOS 26 rolls out

[yingxingheiditan]

Hi all,

I have an app that uses "@react-native-google-signin/google-signin": "^16.0.0" for users to link their google drive and upload files to our app. It was working well up until IOS 26 rolls out. Now our app suddenly became very laggy and we were also not able to upload some files from Google Drive. We also have desktop and Android applications that uses the same package and function well (we use Expo Go for mobile apps and Vue.js/ Quasar for windows), we only encounter this issue on IOS.

I think that its a integration/auth flow issue with how the @react-native-google-signin/google-signin client is being used (silent sign-in, repeated configure, token refresh timing) than a Google Drive API problem. Any ideas on how to fix this or a workaround for this issue? Did anyone also encounter the same issue?

[pratikrath126]

Hey! That sounds like a frustrating build break. Have you tried updating the library to the latest version or running pod update in your ios directory? Sometimes new iOS rollouts require updated native dependencies to handle changes in the build toolchain or SDKs. Since you mentioned silent sign-in and repeated configure, it might be worth verifying if the configuration is being called more than once unnecessarily, as that can sometimes cause race conditions or performance hits on iOS. If you can share any specific error logs from Xcode, it might be easier to pinpoint the cause!

[yingxingheiditan]

Hey, thank you for the suggestions!
I have done some more digging and realized that my Android app was actually facing the same issues 🥲, and my Windows app was using the wrong scope (outside users were not able to access their Google Drive), when I switched to the correct scope, the same error occurred.

I realized that Google has updated their Google Drive API at 25 February (where the app started to break), so this is not a package related issue then...

I will open this issue to Google instead, thank you!