Repository navigation
feat(ios): prefer Yunlefun app authorization - #223
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Deploying cook with
|
| Latest commit: |
4efcc4a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5fc40468.cook-7xl.pages.dev |
| Branch Preview URL: | https://codex-ios-yunlefun-app-first.cook-7xl.pages.dev |
This branch was successfully deployed
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
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.
When a user taps “登录云乐坊账号”, Cook now attempts YunLeFun’s existing
/auth/appUniversal Link. If iOS cannot open the app, Cook uses its existing system web authentication. A user waiting for the app can also cancel or switch to the web; switching invalidates the previous attempt.The return URL,
cook-mobileregistration, and code exchange are unchanged. Cook’s AASA adds only the native authorization callback and retains the WeChat path and web credentials. No changes to website WeChat login, CloudBase configuration, or the native WeChat integration in #222.Validated: 18 iOS tests covering the account store, protocol, callback routing, app-first success, web fallback, and stale callbacks. Before release, publish Cook’s AASA and verify app-to-app return and web fallback on a physical iPhone. Related to #221.