403 error again - Githubissues

gregoryh325 commented 3 months ago

Checklist

[X] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
[X] I have read the FAQ and my problem isn't listed.
[X] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
[X] This issue contains only one bug.

Affected version

Beta 22.77 and stable 22.74

Device Type

Smart TV/Box

Affected Android

Android TV 11

Steps to reproduce the bug

403 error started again today on stable and beta latest versions

Actual behavior

No response

Additional information

Video never starts then 403 error popup

reyzor-q commented 3 months ago

Same issue here

AnthonyA1223 commented 3 months ago

Same, casting from my phone (youtube app) to smartTube works though, using that as a workaround.

ubiquitas commented 3 months ago

me too. On 22.74 Nvidia Shield

LimesKey commented 3 months ago

same

Shadowmaster16 commented 3 months ago

It works fine. Start a new video and wait. The program tried different methods by itself. After 4-5 attempts, it played the video. Later, it worked without testing and chose the right playback method.

therealdrl commented 3 months ago

It works fine. Start a new video and wait. The program tried different methods by itself. After 4-5 attempts, it played the video. Later, it worked without testing and chose the right playback method.

100% accurate. Open a video, then put the remote down and wait. Don't back out. It'll spinwheel 4-5 times in succession and throw up the 403 error a few times, then load the video.

ubiquitas commented 3 months ago

thanks, seems patience is key - works for me too

gregoryh325 commented 3 months ago

That's not true---waiting. I did wait on several videos. They don't play and I get a 403 error popup box

Shadowmaster16 commented 3 months ago

That's not true---waiting. I did wait on several videos. They don't play and I get a 403 error popup box

No, just wait 1-3 minutes for a video. It tries several variants and shows a 403 error multiple times, but eventually it plays the video and saves that.

NoMeNoMeNo commented 3 months ago

It works fine. Start a new video and wait. The program tried different methods by itself. After 4-5 attempts, it played the video. Later, it worked without testing and chose the right playback method.

I think you may have mistaken what the real issue is.

The problem is that resolution is now capped at 1080P and VP9 is locked out.

The fix will return 4K and VP9 decoding.

thoots99 commented 3 months ago

I have been getting the latest releases, like the one "only if you're having problems." Because "I have been having problems." Like the following:

Unknown source error Invalid integer size: 525

Unknown source error Invalid integer size: 52

Unknown source error Invalid float size size: 1904833

Unknown source error Unexpected IllegalStateException: No valid varint length mask found

Unknown source error Invalid integer size: 196074

And so on. Along with the usual 403 error. I would say that this ONLY happens at the beginning of playback, occasionally. Certainly not "every time." Just occasionally. And yes, if any of these "won't start playback," I quickly learned to "just wait," and the video would start playing, eventually. Certainly within, say half a minute at most.

Hope this helps.

ACR-Jeff commented 3 months ago

I had 1 403 error on the previous version, Then updated to the new recent version 22.78 Beta of ST, Now getting 403 loops followed by spinning wheel.

mindforger commented 3 months ago

That's not true---waiting. I did wait on several videos. They don't play and I get a 403 error popup box

No, just wait 1-3 minutes for a video. It tries several variants and shows a 403 error multiple times, but eventually it plays the video and saves that.

I can confirm, hitting play a few times fixed it for me too

NoMeNoMeNo commented 3 months ago

I just tested 22.79 Beta, and it did not fix the 1080P cap.

To reiterate, 22.79 Beta does NOT fix 4K/VP9.

Grannky commented 3 months ago

It works fine. Start a new video and wait. The program tried different methods by itself. After 4-5 attempts, it played the video. Later, it worked without testing and chose the right playback method.

I think you may have mistaken what the real issue is.

The problem is that resolution is now capped at 1080P and VP9 is locked out.

The fix will return 4K and VP9 decoding.

I can confirm this, changing resolution and encoding to 1080p avc on video presets removes the 403 as a workaround.

BobbyWibowo commented 3 months ago

Changelog for beta 22.79 explicitly said the temp fix is only up to full hd (1080p) for now. Wait further fixes for higher res.

Grannky commented 3 months ago

Changelog for beta 22.79 explicitly said the temp fix is only up to full hd (1080p) for now. Wait further fixes for higher res.

I think the main problem is that the update in itself does not force 1080p avc default, until the issue is resolved, so people are just applying the update and not looking at notes and in my case I assumed it was the supported resolution and encoding was being forced upon patching.

NoMeNoMeNo commented 3 months ago

Changelog for beta 22.79 explicitly said the temp fix is only up to full hd (1080p) for now. Wait further fixes for higher res.

I understood that, but in the past I believe “FULLHD” was the terminology used to signify 4K as opposed to “HD” which meant 1080P.

.

albino1 commented 3 months ago

They acknowledged the new problem on their patreon and said they are currently working on a fix:

https://www.patreon.com/smarttube/posts

Generator commented 3 months ago

Im on 2.74 Stable, it shows some 403 but it's playing with 720p AVC/opus

@NoMeNoMeNo HD = 720p FullHD = 1080p UltraHD = 4K/8K

https://en.wikipedia.org/w/index.php?title=Ultra-high-definition_television

NoMeNoMeNo commented 3 months ago

@NoMeNoMeNo HD = 720p FullHD = 1080p UltraHD = 4K/8K

https://en.wikipedia.org/w/index.php?title=Ultra-high-definition_television

That's understood.

I don't think I've ever seen a changelog using the term “UltraHD”, but I could be wrong.

.

Grannky commented 3 months ago

@NoMeNoMeNo HD = 720p FullHD = 1080p UltraHD = 4K/8K https://en.wikipedia.org/w/index.php?title=Ultra-high-definition_television

That's understood.

I don't think I've ever seen a changelog using the term “UltraHD”, but I could be wrong.

.

It's kind of understandable what the term UHD is, it's a term referring to above the standardised 1080 for FHD, 4K , 8K and coming in 2060 26K.

The term UHD is a temporal placeholder for things above 1080p until 4K becomes standard in around 10 years.

Then 1080p becomes 720p 720 becomes 480p ( or whatever )

Around, Around we go....

lde commented 3 months ago

Hi Here more details about Issue on my side

07-31 22:05:29.107 14251 14365 E ExoPlayerImplInternal: Source error. 07-31 22:05:29.107 14251 14365 E ExoPlayerImplInternal: com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 403 07-31 22:05:29.107 14251 14365 E ExoPlayerImplInternal: at com.google.android.exoplayer2.ext.cronet.CronetDataSource.open(CronetDataSource.java:356) 07-31 22:05:29.107 14251 14365 E ExoPlayerImplInternal: at com.google.android.exoplayer2.upstream.DefaultDataSource.open(DefaultDataSource.java:257) 07-31 22:05:29.107 14251 14365 E ExoPlayerImplInternal: at com.google.android.exoplayer2.upstream.StatsDataSource.open(StatsDataSource.java:83) 07-31 22:05:29.107 14251 14365 E ExoPlayerImplInternal: at com.google.android.exoplayer2.source.chunk.InitializationChunk.load(InitializationChunk.java:77) 07-31 22:05:29.107 14251 14365 E ExoPlayerImplInternal: at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:394) 07-31 22:05:29.107 14251 14365 E ExoPlayerImplInternal: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 07-31 22:05:29.107 14251 14365 E ExoPlayerImplInternal: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 07-31 22:05:29.107 14251 14365 E ExoPlayerImplInternal: at java.lang.Thread.run(Thread.java:923)

After 3 Burger notification video start without doing anything.

Occurs only once by app Lunch

Impact on usage is low.

Thanks to devs. I just subscribed to Patreon : https://www.patreon.com/smarttube/ Take Care. Great App !

lde commented 3 months ago

22.79 version of the app fixed the issue on my side.

ACR-Jeff commented 3 months ago

22.79 version of the app fixed the issue on my side.

Yes came here to say the same, Thank you to the devs. Awesome as always.

GreenBeanMech commented 3 months ago

22.80 still giving 403 with this video on my Nvidia Shield, any other platforms feel free to test

It has a warning on desktop that I'm wondering isn't being handled correctly

Edit: 22.81 fixed this, Thank You!

hiroober commented 3 months ago

22.81 started to get error 403 since last night. I'm so sad...

lde commented 3 months ago

I'm not able to reproduce error on 22.80 or 22.81. I seems google is doing testing on cohorts of accounts.

allenzhang3305 commented 3 months ago

22.81 same error

Katerle commented 3 months ago

22.81 Stable and Beta, FireTV, logged in, error 403 on first vid after starting app, it takes a litte time (around 30 seconds), then vid plays. After that all others no problem. Short: 1st vid after app-start, be patient, then it works.

Sahilluci commented 3 months ago

I had same issue but I will check

yuliskov / SmartTube

403 error again #3789

Checklist

Affected version

Device Type

Affected Android

Steps to reproduce the bug

Actual behavior

Additional information