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

Cannot load channel's metadata using channel handle #175

Open
LazytownSpo666 opened this issue May 22, 2024 · 5 comments
Open

Cannot load channel's metadata using channel handle #175

LazytownSpo666 opened this issue May 22, 2024 · 5 comments

Comments

@LazytownSpo666
Copy link

LazytownSpo666 commented May 22, 2024

When i input the YouTube channel link with channel handle on MW Metadata (for example: www.youtube.com/@channel_handle) and i clicked "Submit", it could not be loaded. What happened?!

@mattwright324
Copy link
Owner

Hi @LazytownSpo666,

Are you able to share the specific channel url you used and is the channel still accessible (not terminated)? It is working fine for me currently

@LazytownSpo666
Copy link
Author

Hi @LazytownSpo666,

Are you able to share the specific channel url you used and is the channel still accessible (not terminated)? It is working fine for me currently

i tried everything, even waiting for few days, and it still refuses to resolve and load any metadata of a channel with custom channel handle.

Also i checked the developer tools console, and it stuck on "Attempting to resolve channel handle via CORS" and IT REFUSES TO RESOLVE, INSTEAD THEY GO ON, AND ON, AND ON!!!

It WOULD be nice to fix this issue. Is it my problem, or an issue with CORS?!

@mattwright324
Copy link
Owner

Sounds like some kind of issue on your end, still working fine for me. It's calling my heroku service cors-proxy-mw324.herokuapp.com to resolve the channel id. What browser are you using and are there any extensions that might not like herokuapp for some reason?

@LazytownSpo666
Copy link
Author

LazytownSpo666 commented Jun 5, 2024

Sounds like some kind of issue on your end, still working fine for me. It's calling my heroku service cors-proxy-mw324.herokuapp.com to resolve the channel id. What browser are you using and are there any extensions that might not like herokuapp for some reason?

Any browsers, including Chrome for Mobile. Also extensions are not supported for the latter.

@LazytownSpo666
Copy link
Author

Hello? are you replying to me?!

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

2 participants