fix: refreshing tokens at the wrong time (#55)

fix: refreshing tokens at the wrong time

StoredSession.isValid was being calculated incorrectly, because by comparing to “1 minute ago”, it means an access token which expires “30 seconds ago” is still valid for 30 seconds. Changing to plus 60 seconds eliminates this problem, and bakes in plenty of time for latency issues.

In a future evolution I believe this value should be configurable.

configurable refresh tolerance
Revert “configurable refresh tolerance”

This reverts commit 942acce3e534a508fa8483f17c71d11e459ef587.

`gotrue-swift`

Swift client for the GoTrue API.

Using

The usage should be the same as gotrue-js except:

Oauth2:

signIn with OAuth2 provider only return provider url. Users have to launch that url to continue the auth flow.
After receiving callback uri from OAuth2 provider, use session(from url: URL) to parse session data.

Running Examples

For running the examples project you’ll have to provide your own Supabase project.

$ cp Examples/Shared/Sources/_Secrets.swift Examples/Shared/Sources/Secrets.swift
$ Examples/Shared/Sources/Secrets.swift # Or use you favorite editor

Replace {PROJECT_ID} and {ANON_KEY} with real values for your project on the Supabase portal.

Check Examples for example usages.

Contributing

Fork the repo on GitHub
Clone the project to your own machine
Commit changes to your own branch
Push your work back up to your fork
Submit a Pull request so that we can review your changes and merge

License

This repo is licensed under MIT.

Credits

https://github.com/supabase/gotrue-js - ported from supabase/gotrue-js fork
https://github.com/netlify/gotrue-js - original library