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

get_history() fails #298

Closed
atlasrule opened this issue Sep 23, 2022 · 3 comments
Closed

get_history() fails #298

atlasrule opened this issue Sep 23, 2022 · 3 comments
Labels
yt-update A server-side change caused this issue

Comments

@atlasrule
Copy link
Contributor

Function get_history() started returning empty array, while history is not empty. No authentication problems.

Program raises this:
Item 2: 'overlay'
Item 3: 'overlay'
Item 2: 'overlay'
Item 3: 'overlay'
.
.

atlasrule added a commit to atlasrule/ytmusicapi that referenced this issue Sep 23, 2022
Checking if nested objects absent solved solved my issue, sigma67#298
I'm not sure if it's suitable.
@sigma67 sigma67 linked a pull request Sep 23, 2022 that will close this issue
@sigma67 sigma67 added the yt-update A server-side change caused this issue label Sep 23, 2022
@sigma67
Copy link
Owner

sigma67 commented Sep 23, 2022

I'm not seeing this issue on my end. Has the response format changed?

@atlasrule
Copy link
Contributor Author

Hi @sigma67, first thing came to my mind was response format change, haven't checked the code for weeks prompted that my authentication has expired, probably due to logout. Faced the issue after I renewed my credentials. But I can't say if there's any format change.

sigma67 pushed a commit that referenced this issue Oct 1, 2022
Checking if nested objects absent solved solved my issue, #298
I'm not sure if it's suitable.
@sigma67
Copy link
Owner

sigma67 commented Oct 1, 2022

merged in 7de7ecf

@sigma67 sigma67 closed this as completed Oct 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
yt-update A server-side change caused this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants