v7 API now breaks with "code":"Unauthorized","description":"Invalid Cookie"
kamoco opened this issue · 16 comments
Can you please convert it to v6. V6 works.
I have the same issue. What do you mean by "convert it to v6"?
never mind. Found it (at least I think). You meant to change the URL to use V6 instead of V7
I cloned the project and added optional parameters to select the api version. It works fine with v6 as suggested by @kamoco. However, I don't have permissions to push my branch and create a PR.
sorry for the late reply. Yes change the url to v6. I could not create a new package that worked otherwise I would have shared that.
Hi anyone that can create dll and share it? Thanks
It uses v6 as default and you also have an optional parameter to select a different version in all public methods which do a request. Just in case the working version changes again.
It uses v6 as default and you also have an optional parameter to select a different version in all public methods which do a request. Just in case the working version changes again.
Thanks if i pass ApiVersion.V6 like parameter i get the error: Failure to create client.
Looks like v6 is not working now. Is it working for you guys? I am getting
{"finance":{"result":null,"error":{"code":"Not Found","description":"HTTP 404 Not Found"}}}
same year, v6 stopped working. Any solution/workaround?
might explain!
I got it working with v7 using this workaround.
I also updated all nuget packages to most recent version to keep this code somewhat current. Unfortunately, that broke Flurl cookies handling and SVC parsing, so I had to fix those as well.
Here is the PR #55 for the fixes. @karlwancl or others, please review and approve.
I can do screen sharing to review these changes if needed.
Hi @sergemat
Thanks for your contribution on this project. I'm no longer using Yahoo finance anymore and this project has been unmaintained for a while.
If you really wish to help and do the update, I can give you the collaborator role so you could help to update it accordingly. Are you okay with that?
Hi @karlwancl. Yes, please do. I'm still using it :).
@karlwancl the deployment fails due to outdated nuget API Key. I don't have access to the repo settings to assign a new one. Please update the key.