mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: Unable to set positionTicks for an item via API_KEY #4774
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @luigi311 on GitHub (Apr 7, 2023).
Please describe your bug
I am unable to set the positionTicks for an item for a user via the api key from the server. Using a delete request as following /Users/{userId}/PlayingItems/{itemId}?positionTicks={positionTicks} via a user token works but using that same request with a api key from the server does not. It also doesnt seem like theres any way to generate a user token via the api key so it doesnt look like theres a way to handle it that way either.
The logs report that the playback was stopped for the correct item at the correct time but since its with a api key it doesnt seem to handle it correctly even though the request has the user id in it so it should know who this belongs to.
Jellyfin Version
10.8.0
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@jellyfin-bot commented on GitHub (Aug 6, 2023):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@luigi311 commented on GitHub (Aug 6, 2023):
This is still an issuee
@jellyfin-bot commented on GitHub (Dec 6, 2023):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@luigi311 commented on GitHub (Dec 6, 2023):
this is still an issue
@chuckgmthompson commented on GitHub (Mar 14, 2024):
+1
@jellyfin-bot commented on GitHub (Jul 13, 2024):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@luigi311 commented on GitHub (Jul 15, 2024):
This was resolved in 10.9