为何Google示例代码在FUIAuth处理失败时回退到GIDSignIn处理？

Great question—this is a smart reliability choice baked into the Friendly Pix iOS app's auth flow. Let’s break down the reasoning step by step:

1. FirebaseUI Auth (FUIAuth) is an abstraction, not a replacement for native SDKs #

FUIAuth (part of FirebaseUI) is designed to simplify integrating multiple auth providers (like Google, Facebook) into your app with minimal code. It wraps native provider SDKs (like GIDSignIn for Google) to create a unified flow. However, this abstraction means it doesn’t handle every single edge case that the native SDKs support.

For example:

• Platform-specific OAuth errors
• Device-specific auth quirks (like Safari Services issues on older iOS versions)
• Advanced provider-specific flows that FirebaseUI doesn’t expose

2. GIDSignIn is Google’s official, granular auth tool #

GIDSignIn is the native Google Sign-In SDK for iOS. It’s built to handle every possible scenario for Google auth, including edge cases that FirebaseUI’s wrapper might miss. When FUIAuth hits a failure it can’t resolve, falling back to GIDSignIn ensures users still have a path to authenticate.

3. The fallback acts as a reliability safety net #

Looking at the code snippet you shared, the app configures FUIAuth with FUIGoogleAuth() as a provider. If that flow fails (say, a network error mid-sign-in, or a FirebaseUI-specific bug), the app triggers GIDSignIn directly. This is a deliberate choice to:

• Reduce auth failure rates for users
• Ensure compatibility with a wider range of devices and network conditions
• Avoid relying entirely on a third-party wrapper for critical user functionality

In short, the fallback balances the convenience of FirebaseUI with the robustness of the native Google Sign-In SDK, creating a more reliable auth experience.

内容的提问来源于stack exchange，提问作者Ted Hopp