|
3 | 3 | [](https://cocoapods.org/pods/GoogleSignIn) |
4 | 4 | [](https://github.com/google/GoogleSignIn-iOS/actions/workflows/tests.yml) |
5 | 5 |
|
6 | | -# Google Sign-In for iOS |
| 6 | +# Google Sign-In for iOS and macOS |
7 | 7 |
|
8 | 8 | Get users into your apps quickly and securely, using a registration system they |
9 | 9 | already use and trust—their Google account. |
@@ -49,8 +49,17 @@ If you would like to see a Swift example, take a look at |
49 | 49 | * Take a look at the |
50 | 50 | [API reference](https://developers.google.com/identity/sign-in/ios/api/). |
51 | 51 |
|
52 | | -## Mac Catalyst |
| 52 | +## Google Sign-In on macOS |
53 | 53 |
|
54 | | -Google Sign-In supports apps built for [Mac Catalyst](https://developer.apple.com/mac-catalyst/). In order for |
55 | | -your Mac Catalyst app to access the keychain on macOS you will need to enable the Keychain Sharing capability. No |
56 | | -keychain groups need to be added. |
| 54 | +Google Sign-In allows your users to sign-in to your native macOS app using their Google account |
| 55 | +and default browser. When building for macOS, the `signInWithConfiguration:` and `addScopes:` |
| 56 | +methods take a `presentingWindow:` parameter in place of `presentingViewController:`. Note that |
| 57 | +in order for your macOS app to store credientials via the Keychain on macOS, you will need to |
| 58 | +[sign your app](https://developer.apple.com/support/code-signing/). |
| 59 | + |
| 60 | +### Mac Catalyst |
| 61 | + |
| 62 | +Google Sign-In also supports iOS apps that are built for macOS via |
| 63 | +[Mac Catalyst](https://developer.apple.com/mac-catalyst/). In order for your Mac Catalyst app |
| 64 | +to store credientials via the Keychain on macOS, you will need to |
| 65 | +[sign your app](https://developer.apple.com/support/code-signing/). |
0 commit comments