-
Notifications
You must be signed in to change notification settings - Fork 13
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
https://habitica.com/apidoc/ Just continually loads #36
Comments
@cTheDragons It's your chat extension. It's erroring because javascript it expects to be on the page is not on the page. |
The fix would be to limit the chat extension to the website proper, instead of hitting all the subdomains. (which is out of our domain, I'm afraid) I'll email @horacious about it |
Thanks using a private window fixed this too. |
Actually, scratch what I said about domains (although that is also true), that wouldn't work in this case since /apidoc is on the same domain. |
I'm reopening this because cTheDragons says it's still happening. It might end up being something that needs to be fixed in HabitRPG's Habitica Chrome chat extension but if so we can move this issue to that repo. |
It loads fine for me so I think it's an issue with the chat extension, @cTheDragons can you try to disbale it and see if it works? And if you can grab the console logs it would be great. And yes I think it should be moved in the chat extension repo |
Yes, currently it only not working with the Chat Client enabled, including the latest one. This is the error I have:
This is the errors I get when running successfully:
|
It looks like the transfer wasn't successful earlier and it closed the issue instead. It's a beta feature so |
This can be closed now as it has been fixed with Pull Request #37. |
General Info
Description
When going to the URL Address https://habitica.com/apidoc/ I just get a continuous loading screen, that is it never shows itself.
(I have tried multiple times and the last attempt I waited over an hour for any results).
The text was updated successfully, but these errors were encountered: