You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Copy the generated secret (you'll need it for the app)
41
+
- Click **"Save and deploy"**
35
42
36
43
### 3. Calendar Notifications Plus Configuration
37
44
@@ -41,7 +48,9 @@ This guide will help you set up data synchronization for Calendar Notifications
41
48
- Supabase URL (from step 1.3)
42
49
- Supabase Anon Key (from step 1.3)
43
50
- PowerSync Instance URL (from step 2.2)
44
-
- PowerSync Token (from step 2.4)
51
+
- PowerSync Token (paste the same HS256 secret from step 2.4)
52
+
53
+
> **Note:** The app automatically generates short-lived JWT tokens (5 min expiry) using this secret. The JWTs include `sub` (device ID), `aud` (powersync), `iat`, and `exp` claims. Unlike development tokens, the HS256 secret doesn't expire - you only need to configure it once.
45
54
46
55
## Verification
47
56
@@ -55,6 +64,10 @@ This guide will help you set up data synchronization for Calendar Notifications
55
64
- Check the PowerSync status in the app
56
65
- Ensure your Supabase and PowerSync instances are running and connected
57
66
- Review the app logs for any error messages
67
+
-**JWT errors:** Make sure the HS256 secret in the app matches exactly what's configured in PowerSync dashboard
68
+
-**"Invalid token" errors:** Verify the HS256 secret is properly configured under Client Auth → HS256 authentication tokens
69
+
-**"Missing aud claim" errors:** Add `powersync` to JWT Audience in the PowerSync dashboard (Client Auth → JWT Audience)
70
+
-**"Unexpected aud claim" errors:** The JWT Audience in PowerSync dashboard must include `powersync`
0 commit comments