fix: keep Seedance authorization cross-device - #18
Merged
Conversation
Deploying new-api with
|
| Latest commit: |
250cdf6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://55be2544.new-api-d57.pages.dev |
| Branch Preview URL: | https://agent-seedance-user-authoriz.new-api-d57.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed\n\n- extend the local authorization session and desktop polling window from 5 to 15 minutes\n- keep the mobile callback on a public completion page with no Token123 login link\n- clarify that the phone can be closed after liveness verification while the original device continues automatically\n- update all frontend locales, documentation, tests, and tracked production assets\n\n## Root cause\n\nThe desktop discarded the short-lived BytedToken after five minutes, so a liveness flow with an action retry could complete on the phone after Token123 had already stopped polling. The callback page also linked mobile users into the authenticated console, which unnecessarily prompted them to sign in.\n\n## Validation\n\n- go test ./... -count=1\n- bun test (13 passed)\n- targeted Prettier check\n- production Vite build and referenced-asset verification\n\nThe repository-wide i18n linter still reports 98 pre-existing issues; this change adds no new reported i18n issue.