Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Immediate redirect from wit.ai/apps/[appID]/understanding to wit.ai/apps/ #2738

Open
Virus-vr opened this issue Jul 26, 2024 · 1 comment
Open

Comments

@Virus-vr
Copy link

Do you want to request a feature, report a bug, or ask a question about wit?
Report a bug

What is the current behavior?
Once I click on my app it immediately redirects me to to apps page again.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Use opera or chrome on a windows pc. Click on any app from the apps page or the understandings page directly. Now you should get redirected back to the apps page.
Additional information:

It does work as expected/normally on my phone (chrome)
I disabled all extensions to trouble shoot this.
When I go directly to wit.ai/apps/[appID]/insights I can stay there.
This sounds very similar to this issue to me #2128 , as I can also see a write line in that field when getting redirected.

I'm getting these errors in the console: (note that I think I'm getting these errors from the apps page and not the /understandings page, but I don't know.

Error with Permissions-Policy header: Unrecognized feature: 'battery'.
Error with Permissions-Policy header: Unrecognized feature: 'usb-unrestricted'.
sdk.js:22 [Report Only] This document requires 'TrustedScriptURL' assignment.
_ @ sdk.js:22
(anonymous) @ sdk.js:22
O0LUcMm8sJs.js?_nc_x=Ij3Wp8lg5Kz:55 [Report Only] This document requires 'TrustedHTML' assignment.

What is the expected behavior?
To stay on the understandings page.

If applicable, what is the App ID where you are experiencing this issue? If you do not provide this, we cannot help.
All of them. I tried to create a few more to see if setting it to public/private changes anything.
Here is one 802406751878038

@Virus-vr
Copy link
Author

Virus-vr commented Jul 28, 2024

Today the problem seams to be gone. I'm not sure what I changed.
Should I close this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant