Lemmy App Development

746 readers

1 users here now

A place for Lemmy builders to chat about building apps, clients, tools and bots for the Lemmy platform.

On-Topic:

programming questions related to the Lemmy platform
sharing your ideas, WIP, or released Lemmy-related work

Off-Topic:

general programming questions unrelated to Lemmy
feature requests for developers
sharing or promoting work not related to Lemmy

founded 2 years ago

MODERATORS

[email protected]

[SOLVED] Error "user_already_exists" from saveUserSettings (self.lemmydev)

submitted 2 years ago* (last edited 2 years ago) by silas to c/[email protected]

3 comments fedilink hide all child comments

I'm getting a "user_already_exists" error from /user/save_user_settings no matter what settings I try to change. The JWT is valid, and this is happening on multiple instances the same (programming.dev, lemm.ee, etc.) Anyone have any ideas why I'd be getting this? Here's my payload:

{
  show_bot_accounts: true,
  auth: token
}

Edit: This issue describes a bug where this happens when the avatar field is not included. Just tested it and that's the same problem I'm running into. I fixed it temporarily by passing the current avatar url.

top 2 comments

sorted by: hot top controversial new old

[–] [email protected] 3 points 2 years ago* (last edited 2 years ago) (1 children)

I also found this exact error happens if you change nothing! The error is confusing.. if you set a setting to the same value (true, false, false all in a row). I actually consider that buggy, as with all the server crashes retries to the API are kind of the norm in July ;)

[–] silas 2 points 2 years ago

I know, we're all here trying to find temporary workarounds for these types of things haha, it'll get better

load more comments