mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 01:45:10 +03:00
chore(docs): general improvements to Swift guides (#22627)
This commit is contained in:
1 parent
69ad842814
commit
dca045048f
3 files changed
+4
-4
No files matched your search
@@ -169,7 +169,7 @@ await supabase.auth.linkIdentity(OAuthProvider.google);
|
||||
</TabPanel>
|
||||
<TabPanel id="swift" label="Swift">
|
||||
|
||||
You can use the [`linkIdentity()`](/docs/reference/swift/auth-linkidentity) method to link an oauth identity to the anonymous user.
|
||||
You can use the [`linkIdentity()`](/docs/reference/swift/auth-linkidentity) method to link an OAuth identity to the anonymous user.
|
||||
|
||||
```swift
|
||||
try await supabase.auth.linkIdentity(provider: .google)
|
||||
|
||||
@@ -126,7 +126,7 @@ Future<void> signInWithEmail() async {
|
||||
</TabPanel>
|
||||
<TabPanel id="swift" label="Swift">
|
||||
|
||||
When your user signs in, call [signInWithPassword()](/docs/reference/swift/auth-signinwithpassword) with their email address and password:
|
||||
When your user signs in, call [signIn(email:password:)](/docs/reference/swift/auth-signinwithpassword) with their email address and password:
|
||||
|
||||
```swift
|
||||
try await supabase.auth.signIn(
|
||||
@@ -185,7 +185,7 @@ Future<void> signOut() async {
|
||||
</TabPanel>
|
||||
<TabPanel id="swift" label="Swift">
|
||||
|
||||
When your user signs out, call [signOut()](/docs/reference/swift/auth-signout) to remove them from the browser session and any objects from localStorage:
|
||||
When your user signs out, call [signOut()](/docs/reference/swift/auth-signout) to remove the session from the local storage:
|
||||
|
||||
```swift
|
||||
try await supabase.auth.signOut()
|
||||
|
||||
@@ -19,7 +19,7 @@ Set up Magic Link logins for your Supabase application.
|
||||
|
||||
When using Magic Links in [the PKCE Flow](/blog/supabase-auth-sso-pkce#introducing-pkce), keep in mind that links can only be opened from the same browser that they are sent from (as defined in the PKCE spec). Consequently, a magic link sent from Chrome on Desktop will be invalid if used on a Mobile Device.
|
||||
|
||||
The same applies for Magic Links in mobile devices, magic link can only be opened on the same device that originated it.
|
||||
The same applies for Magic Links in mobile devices. Magic Links can only be opened on the device they are sent from.
|
||||
|
||||
</Admonition>
|
||||
|
||||
|
||||
Reference in new issue
Block a user