New API Key with Legacy JWT on mobile migration
Hello! We’re upgrading our production iOS app from legacy anon keys to the new sb publishable key. We don’t plan to migrate to JWT signing keys yet.
Can you confirm that:
1. existing user JWTs remain valid and users won’t be logged out, and can use the app to sign in / sign up with it
2. both old (legacy anon) and new (publishable sb) keys can coexist so that older app builds continue to work until we disable legacy keys?
Scenario:
Version A: Use legacy Key
Version B: WIll use publishable key
Both can still use the app normally in any auth actions
Thank you!
Can you confirm that:
1. existing user JWTs remain valid and users won’t be logged out, and can use the app to sign in / sign up with it
2. both old (legacy anon) and new (publishable sb) keys can coexist so that older app builds continue to work until we disable legacy keys?
Scenario:
Version A: Use legacy Key
Version B: WIll use publishable key
Both can still use the app normally in any auth actions
Thank you!
