-
Notifications
You must be signed in to change notification settings - Fork 680
Description
đ CheckList
- I have searched existing issues to avoid duplicates
- I am using a recently maintained version of Coze Loop
- I have provided all required information
- I understand this is a bug report and not a feature request
- I have submitted this report in English (otherwise it will not be processed)
đ Bug Description
I am currently integrating CozeLoop into my own platform. When using CozeLoop, the frontend needs to redirect to a CozeLoop webpage. However, since CozeLoopâs interface requires cookie information, the redirection fails. How should I resolve this issue? Can I completely remove CozeLoopâs interface authentication?
đ Steps to Reproduce
I am currently integrating CozeLoop into my own platform. When using CozeLoop, the frontend needs to redirect to a CozeLoop webpage. However, since CozeLoopâs interface requires cookie information, the redirection fails. How should I resolve this issue? Can I completely remove CozeLoopâs interface authentication?
â Expected Behavior
I am currently integrating CozeLoop into my own platform. When using CozeLoop, the frontend needs to redirect to a CozeLoop webpage. However, since CozeLoopâs interface requires cookie information, the redirection fails. How should I resolve this issue? Can I completely remove CozeLoopâs interface authentication?
â Actual Behavior
I am currently integrating CozeLoop into my own platform. When using CozeLoop, the frontend needs to redirect to a CozeLoop webpage. However, since CozeLoopâs interface requires cookie information, the redirection fails. How should I resolve this issue? Can I completely remove CozeLoopâs interface authentication?
đ¨ Severity
None
đ§ Component
None
đť Environment
No response
đ§ Go Environment
No response
đ Logs
đ Additional Context
No response