I'm a bit confused about how this lib is supposed to be used for signing in via a Provider (e.g. Google Oauth).

As mentioned by this issue in the supabase/supabase repo (see screenshot below) callbacks come with params as a fragment, not a query.

However this lib asserts that a query is required to parse a Provider based sign-in: https://github.com/supabase-community/gotrue-swift/blob/5a5aca5aa63fbb4639458dc0c044f17586c3c9d7/Tests/GoTrueTests/GoTrueTests.swift#L45-L68

So the following code fails:

func authenticate() {
  let client = SupabaseClient(supabaseUrl: host, supabaseKey: clientId)

  client.auth.signIn(provider: .google, options: .init(redirectTo: "my-app://supabase-oauth-callback", scopes: nil)) { authReslt in
    switch authReslt {
    case .success(let url):
      let session = ASWebAuthenticationSession(url: url, callbackURLScheme: "my-app") { callbackUrl, error in
        guard error == nil, let callbackUrl = callbackUrl else { return } // handle this error case

        // will fail on the line below because the url will be `my-app//supabase-oauth-callback#access_token=.....`
        // rather than `my-app//supabase-oauth-callback?access_token=.....`
        client.auth.getSessionFromUrl(url: callbackUrl.absoluteString) { sessionResult in
          switch sessionResult {
          case .success:
            // login succeeded
          case .failure:
            // handle login failure           
          }
        }
      }
      
      session.presentationContextProvider = self
      session.start()             
    case .failure:
      continuation.resume(returning: false)
    }
  }
}

This is the exact callbackUrl that this code receives:

my-app://supabase-oauth-callback#access_token=ACCESS_TOKEN&expires_in=3600&provider_token=PROVIDER_TOKEN&refresh_token=REFRESH&token_type=bearer

supabase/supabase discussions/2133

I'm getting error even though account is successfully registered.

Here's my code and the error:

I'm using 0.0.4 and I have no problem when using the account to sign in.

I'd imagine it to be fairly common that when a user of gotrue-swift wants to complete the Partner sign in process and start a session, they don't care about the Session that is created.

Hey,

currently experimenting with google authentication. I am able to retrieve an url after the user logs in via google. Then I am trying to get a session from this url. But it throws me this error:

The data couldn’t be read because it isn’t in the correct format.

This is the URL I get:

myapp://callback#access_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJhdXRoZW50aWNhdGVkIiwiZXhwIjoxNjYwNTIyOTIxLCJzdWIiOiI0NTc1ZTgzOC03NjM4LTQ4ZjgtOGFlMC1mZGNiODk0M2E4MmMiLCJlbWFpbCI6Imdlcm5lci5iYXN0aUBnb29nbGVtYWlsLmNvbSIsInBob25lIjoiIiwiYXBwX21ldGFkYXRhIjp7InByb3ZpZGVyIjoiZW1haWwiLCJwcm92aWRlcnMiOlsiZW1haWwiLCJnb29nbGUiXX0sInVzZXJfbWV0YWRhdGEiOnsiYXZhdGFyX3VybCI6Imh0dHBzOi8vbGgzLmdvb2dsZXVzZXJjb250ZW50LmNvbS9hL0FJdGJ2bWtWWjI5d2stS0pTYVZQQVF0c19oc013Z0c3Rk54dHE5czhpNG4xPXM5Ni1jIiwiZW1haWwiOiJnZXJuZXIuYmFzdGlAZ29vZ2xlbWFpbC5jb20iLCJlbWFpbF92ZXJpZmllZCI6dHJ1ZSwiZnVsbF9uYW1lIjoiU2ViYXN0aWFuIEdlcm5lciIsImlzcyI6Imh0dHBzOi8vd3d3Lmdvb2dsZWFwaXMuY29tL3VzZXJpbmZvL3YyL21lIiwibmFtZSI6IlNlYmFzdGlhbiBHZXJuZXIiLCJwaWN0dXJlIjoiaHR0cHM6Ly9saDMuZ29vZ2xldXNlcmNvbnRlbnQuY29tL2EvQUl0YnZta1ZaMjl3ay1LSlNhVlBBUXRzX2hzTXdnRzdGTnh0cTlzOGk0bjE9czk2LWMiLCJwcm92aWRlcl9pZCI6IjExMTAzNDk1NjQxOTI5OTMyMDI2MCIsInN1YiI6IjExMTAzNDk1NjQxOTI5OTMyMDI2MCJ9LCJyb2xlIjoiYXV0aGVudGljYXRlZCJ9.sCPFtWFCQlFzpfx7PyobNCdnxYJqVgmTVyT5xnzg6IM&expires_in=3600&provider_token=ya29.A0AVA9y1vR1d7i6J7ag2je4YV2pS86q9d-zqsZPpUtO5VCDzZSmfAp2MPav8tGFKTexPlzwipMjDdIaGugS93FQXqJa-Ckk_x_V4GBoTdJbUT0vq90cJ_dX_B173FvKa5tFbueB6hmEBhH8IxHOmI4inliOiBYaCgYKATASATASFQE65dr83WmW95n0vDmiN7M6TAYs6w0163&refresh_token=Tp3Vto4DMhUzkonpf-rwsA&token_type=bearer

Using the latest version. URL Types URL scheme and callbackURLScheme are set to: myapp redirectURL and Redirect URLs in supabase are set to: myapp://callback"

Can anyone help me?

Kind regards Sebastian Gerner

I'm currently facing the problem that users get logged out after the JWT Token expires. I assumed the Token gets automatically refreshed when the autoRefreshToken value is set to true but it doesn't.

Error: PostgrestError(details: nil, hint: nil, code: nil, message: "JWT expired")

Additionally, some of the examples (sign in/sign out) in the README.md are not working with the newest version and other docs are missing (authEventChange for example).

Hi @grsouza, I have this error when using auth.session(from:), do you have any idea what's wrong?

dataCorrupted(Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "identities", intValue: nil), _JSONKey(stringValue: "Index 0", intValue: 0), CodingKeys(stringValue: "id", intValue: nil)], debugDescription: "Attempted to decode UUID from invalid UUID string.", underlyingError: nil))

BTW, I'm updating from 0.0.4 (no error) to 0.0.9 (error).

Also checked in Supabase logs, request has 200 response -- so no problem server-side.

Add FoundationNetworking if available. This is allowing Linux platforms to compile the framework, since the migration of URL-related function to the FoundationNetworking framework. Update the Package.swift to accept the same platforms as supabase-swift.

As a Supabase user, I want to see an explicit code example in Swift, to be able to set up a basic user management within minutes and have a reference to the JS documentation.

Currently the documentation doesn't help me that much as a beginner in Swift and with no experience in JS. I personally liked the introduction in the PostgREST (see https://github.com/supabase-community/postgrest-swift section "Usage") where you get a basic example to keep the connection to a db up and running. I was able to get data within 20 min. of work based on the PostgRest "tutorial".

I wish for a short documentation of getting started with a basic user management:

• Create a user with Supabase by providing an e-mail-address and a password (I assume it's the default).
• Assign a session to a user so she or he can INSERT into a db with authored access only (using Supabase RLS templates).

What does this PR Do?

• Moves session storage away from UserDefaults and into the more secure Keychain.
• Fixes a bug where, after signing out, the user and session variables still held the old data from before signing out.

Why?

The Keychain should be used to store user data such as refresh tokens, access tokens and emails. When this data is stored in UserDefaults it can be stolen quite easily by just reading the public plist file that UserDefaults creates. This can lead to bad actors stealing user tokens with ease and using that to steal private data. This is not good.

Storing this data in the Keychain is the safe alternative. GoTrueKeychain implements the necessary functions for storing and deleting session data from the Keychain, and GoTrueSessionManager manages migrating from UserDefaults to Keychain, and fetching and storing session data using the keychain wrapper.

The Keychain wrapper stores the session data in a service called "supabase.gotrue.swift" so as to separate the keys stored by supabase and the keys stored by the app's developer.

My Keychain implementation also allows for developers to set an accessGroup to store the session data in, which will allow developers to share auth state between the app and extensions such as widgets or Siri Shortcuts. By default the access group is not set and is stored in the default Keychain.

One thing that Supabase could implement that Firebase lacks on iOS is the ability to migrate from one keychain access group to another. Possibly with an API like: auth.migrateFrom(keychainGroup, to) but that can come later. This implementation does allow for flexibility like that in the future.

Fixes #33

What is the current behavior?

The UserIdentity id attribute is currently defined as UUID, but this isn't always true.

What is the new behavior?

Change UserIdentity id type to String

I've isolated the class - and made a complete minimal example using bazel.

git clone https://github.com/wweevv-johndpope/DemoBazel/tree/supabase
./xcodegen app

you may need to enable auto signing of app

Please help - I'm a bit behind on timelines because of this crash.

related - duplicated https://github.com/binaryscraping/swift-composable-keychain/issues/1

(it seems like because the xcframework is not around - the keychain is deallocated - and not retaining itself?) I'm not sure the approach using self inside xcframework is doable?

UPDATE I made this cheatsheet for bazel + XCFRAMEWORKS there's a way to do xcframeworks via zip + sha - but for now just dumping them into repo works for me. https://docs.google.com/presentation/d/1ZYwyA_zHjDugt4UH-APJt4qBSt_fbY_286WrgFQvdfA/edit#slide=id.p

related https://github.com/supabase-community/supabase-swift/issues/38

I don't know why the zombies doesn't work for these xcframeworks... that should stop the deallocation - and allow app to continue...

UPDATE I made some effort to rewire the classes so that a chunk is instantiate from swift file locally from app. Good news is - it doesn't crash.

https://github.com/wweevv-johndpope/DemoBazel/tree/gotrue-swift

it's less than ideal - but can live with it for time being. So there's no supabase.xcframework and there's no gotrue.xcframework

The BUILD files x2 compile the swift files

https://github.com/wweevv-johndpope/DemoBazel/tree/gotrue-swift/GoTrue

https://github.com/wweevv-johndpope/DemoBazel/tree/gotrue-swift/Thirdparty/Supabase

not the bundle is dirty and there's problem some clean up necessary but it's working locally. We need to get the classes working within framework.

Description

GoTrue fails to decode UserIdentity.provider entity.

Fix

Add Provider case phone

public enum Provider: String, Codable, CaseIterable {
 case phone
}

Feature request

Following on the thread in https://github.com/supabase/supabase/discussions/1882 and https://github.com/supabase/supabase/discussions/2805 I looked into adding support for AuthenticationServices and in this regard ASAuthorizationAppleIDCredential.

Is your feature request related to a problem? Please describe.

When GoTrue signs users in using SIWA they're redirected to the OAuth apple site where they sign in and eventually GoTrue received the above parameters, just through the OAuth callback flow. If this flow were to be used on iOS, it would be a very clunky UX, and could be grounds for an iOS app to be rejected from review.

Describe the solution you'd like

I started work on this here: https://github.com/catlan/gotrue-swift/commit/bac99073ad56ce6fa3257f33a22a628a135e0e9a

The problem is that the response I get: "Invalid token: signing method RS256 is invalid"

I'm not too familiar with either Sign in With Apple nor supabase. Any clues on what is required to make this work?