Peter Andrews

If you can reproduce this in a debug build, try setting a breakpoint in GTMAppAuth's `GTMKeychain` implementation in the -setPasswordData:forService:accessibility:account:error: method and check the return value of the `SecItemAdd` call....

@zaidhafeez thanks for the feedback. For anyone who is (or was) experiencing this behavior, could you list all the third-party libraries you're using and how they're being built / linked...

@alperkayabasi could you let me know which (if any) third-party libraries you're using in addition to Google Sign-In? Please see my [previous comment](https://github.com/google/GoogleSignIn-iOS/issues/165#issuecomment-1145137355).

For those who are still seeing this issue, please let me know which versions of GoogleSignIn and GTMAppAuth you're building with.

Not at the moment. Can you tell me more about the type of Unity app you're interested in adding Google Sign-In to?

Are you still able to reproduce the time out error?

Could you rebase this branch against `main` to exclude the already-merged API refactoring changes here?

Have you considered [defining a macro for your extension target](https://stackoverflow.com/a/25048511) and using the preprocessor to exclude the calls to `NS_EXTENSION_UNAVAILABLE` methods in your library at build time?

No plan to support [Carthage](https://github.com/Carthage/Carthage) at this point, but I'll leave this open for feedback.

The error you mention is [an exception from GIDSignIn](https://github.com/google/GoogleSignIn-iOS/blob/3f4c51391b6cba09abd87968d4a89cc0c1d70439/GoogleSignIn/Sources/GIDSignIn.m#L400) and should only be triggered if the app has not declared support for the appropriate custom URL scheme given the configured...