Open 0penSourcerer opened 1 week ago
I have encountered the same thing.
When I delete the user from Wizarr I get the following:
12:17:39 DEBUG https://plex.tv:443 "GET /api/users/ HTTP/1.1" 200 None
12:17:39 DEBUG https://plex.tv:443 "DELETE /api/v2/sharings/xxx HTTP/1.1" 204 0
12:17:39 DEBUG https://plex.tv:443 "GET /api/users/ HTTP/1.1" 200 None
12:17:39 DEBUG https://plex.tv:443 "DELETE /api/home/users/xxx HTTP/1.1" 404 None
And then when I sync the users I get this:
12:18:06 DEBUG https://plex.tv:443 "GET /api/v2/user HTTP/1.1" 200 None
12:18:06 DEBUG Encoding detection: utf_8 is most likely the one.
12:18:06 DEBUG https://plex.tv:443 "GET /api/users/ HTTP/1.1" 200 None
12:18:06 INFO User xxx successfully imported to database
12:18:06 INFO 127.0.0.1 - - [2024-11-20 12:18:06] "GET /api/users/scan HTTP/1.0" 200 270 0.992075
I do see that the result from the https://plex.tv/api/users
does contain this user, so even though they are removed from my Plex server, they still appear in the plex API and therefore get imported.
I did see from the response of the /api/users/
endpoint that the user in question does not have a server section, so this might be a way we can filter out these results:
<User id="xxx" title="xxx" username="xxx" email="xxx" recommendationsPlaylistId="" thumb="https://plex.tv/users/xxx/avatar?c=1714937753" protected="0" home="0" allowTuners="0" allowSync="0" allowCameraUpload="0" allowChannels="0" allowSubtitleAdmin="0" filterAll="" filterMovies="" filterMusic="" filterPhotos="" filterTelevision="" restricted="0"></User>
<User id="xxx" title="xxx" username="xxx" email="xxx" recommendationsPlaylistId="" thumb="https://plex.tv/users/xxx/avatar?c=1729524846" protected="0" home="0" allowTuners="0" allowSync="0" allowCameraUpload="0" allowChannels="0" allowSubtitleAdmin="0" filterAll="" filterMovies="" filterMusic="" filterPhotos="" filterTelevision="" restricted="0">
<Server id="xxx" serverId="xxx" machineIdentifier="xxx" name="xxx" lastSeenAt="1732105087" numLibraries="2" allLibraries="0" owned="1" pending="0"/>
</User>
I would like to add that when that removed user is readded, the user won't get an expiration timer set on them.
I don't know if it has anything to do with the user api, or it just fails to cause the user is already "added". It would be nice if the Server
tags were checked since the new friend system messed everything up.
Are you using the latest release?
Have you checked a bug report doesn't already exist?
What happened?
After deleting a user...
...I get a notification on the screen that the user has been successfully deleted, but after using the "Scan Users" tool...
...the user will be back in the list. The automated Scan Users task will also cause the user to re-appear when it has run.
Virtualisation
Docker
What operating system are you seeing the problem on?
Linux
What browsers are you seeing the problem on?
Chrome
Project Location
Local
Bug Description
Deleting users doesn't seem to be working properly, as users re-appear on the User page after a supposed successful deletion.
Steps to Reproduce
Relevant Log Output
No response