-
Notifications
You must be signed in to change notification settings - Fork 626
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
Can't play video with cellular network #513
Comments
What versions of the library are you running? |
Hi SoneeJohn, I run v2.15.2. |
Can you show me the entire log output? |
This is my code:
And debug log when play with cellular network: |
Can you please use the macOS demo app or the iOS demo app and show me the logs from there? |
It is a very long log. I attach the log file. When I played the video with your iOS demo app, it played successfully. |
Hi SoneeJohn, it sounds weird but I found the problem as this:
the player works well if I don't get the value of '.asset.duration'
I apply this to your iOS Demo app, it happens too. Maybe this is the issue of AVPlayer, not XCDYoutubeKit. |
I run v2.15.2 and it always get 360p |
I'm really stuck in this too long. But I'm not sure it is an issue of XCDYoutubeKit or not. I just need help.
I get the stream URL from XCDYoutubeKit with ONLY (and always) medium quality 360p (I don't know why). The problem is that: when I play long-video (over 1 hour) with the cellular network, the screen is black and no audio. With wifi, it plays pretty well and smooth.
I know I need to get the lower quality 240p stream URL to play with cellular. Or maybe, there is another way to play the higher quality with cellular that I didn't know. I appreciate any suggestion or idea.
And this is what I get in debug:
2020-12-14 19:52:45.521130-0800 BeeMusic[5237:1471647] [avas] AVAudioSessionUtilities.h:106 AudioSessionGetProperty ('crar') failed with error: '!ini'
2020-12-14 19:52:45.521193-0800 BeeMusic[5237:1471647] [avas] AVAudioSession_iOS.mm:2158 AudioSessionGetProperty failed with code: 560557673
Updated:
The text was updated successfully, but these errors were encountered: