-
-
Notifications
You must be signed in to change notification settings - Fork 260
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
Update jellyfin-sdk-kotlin to v1.6.1 #1506
base: master
Are you sure you want to change the base?
Conversation
app/src/main/java/org/jellyfin/mobile/player/source/MediaSourceResolver.kt
Outdated
Show resolved
Hide resolved
Any chance of getting this reviewed again @nielsvanvelzen ? It would be nice to start generating builds from the updated sdk... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not test these changes and only reviewed the usages of the SDK. Those all look fine to me.
Would someone be so kind as to trigger the build and test workflows on this PR? |
GH does not let me trigger the builds so the pull request probably needs to be rebased or have master merged into it. |
Fix build errors and add API authorization headers to exoplayer since the access token is no longer passed via URL for Android Auto. See jellyfin/jellyfin-sdk-kotlin#871
2bd932d
to
ee40bcf
Compare
rebased on master. I think you should be able to trigger the build now @nielsvanvelzen |
Changes
Updated SDK version and fixed build errors.
Also added the API authorization header to exoplayer since the access token is no longer passed via URL for Android Auto (see jellyfin/jellyfin-sdk-kotlin#871).
I have tested the Android Auto functionality and it seems to work fine. The only thing I cannot test and suspect that may not work is casting. Not sure how I would add the header there since CastPlayer cannot use a DataSource.Factory. In google/ExoPlayer#4760 they claim that the receiver app is responsible for authentication. Not sure if this is implemented in jellyfin/jellyfin-chromecast though.