No Playability Status Block - Loading Information for a YouTube Track Failed #690
Comments
|
I can have a look at it later tonight; it is probably something similar in nature to #687. |
|
I was right about to create an issue for this. I just started seeing this error today |
Thanks! Yeah, it's frustrating because I'm sure it's something stupid simple but I couldn't figure it out last night because I couldn't debug the lavaplayer code. Attached is the full error. I'll also be taking another look at it later tonight unless you beat me to it. |
|
I did a quick comparison of the json from my error and the json from #688. The structure up to playabilityStatus is identical. But at the playerResponse level, mine has a few additional fields: playerAds, videoQualityPromoSupportedRenderers, and adPlacements. Pretty much everything else looks the same. I have no idea why it could be throwing this error when the structure up to the playabilityStatus isn't different. But the presence of ad info in my error makes me wonder if this could have anything to do with ads? |
Do you have any error logs or system information to share? I don't even know if it's a code issue at this point. Many others using the same version and getting a response of the same format aren't seeing the same issue as us. |
|
@dolanbernard Here's the stack trace. Before this there are two warning messages: |
|
@dolanbernard Disclaimer, I have no prior experience with handling those youtube jsons but from debugging, it seems like the code here failed to find player and player response: Here's the json it's trying to parse. It tries to look on layer deeper than that top level key
|
|
@dolanbernard Yeah this is exactly the same as #687. @idpromnut Tried your PR from jitpack and it works. I'll watch closly and switch back to main branch after the PR is merged. |
I have a completely different error. It's finding the player response but it isn't finding the block directly under it. But it's interesting to see that your response is also missing the ad related data. I've tried the fix from that other thread and it doesn't change anything. In fact, without that fix, I don't see the same error that you were getting. I'm not even sure what else to try at this point. |
|
Update: I was able to fix the issue by just removing the jitpack repository from my pom.xml. I don't know why, but that's it. I noticed that changes I made to my local repository version of lavaplayer weren't having any effect after publishing. This was frustrating because within my IDE, I could view the lavaplayer source and see my changes there. So the version I could see in the IDE by following links in stack traces and Ctrl+Clicking would have my new code, but this isn't actually the code that was being run for some reason. I figured this out when I noticed that the version in my error messages was 1.3.78. In the version I published locally I had set version to 1.4.0. 1.4.0 was the version I selected in my pom.xml. Somehow though, just because I still had the jitpack repo in my pom.xml it was using the wrong version but not even my IDE was aware of that. I still have no idea what code WAS running in lavaplayer, so I don't even know what the error was or why it was different from the message other people were getting. This was a weird one. I'm gonna close this issue now, but if anybody does run into the same problem I can take a look at it. |
I'm seeing a completely different JSON error than everybody else, apparently. For some reason it looks like it's failing to find the playabilityStatus block but, as far as I can tell from looking at the JSON, it's there. This does not get fixed by merging #687.
The text was updated successfully, but these errors were encountered: