Skip to content

Fix username encoding in PublicKeyCredentialUserEntity - #79

Merged
mkalioby merged 1 commit into
mkalioby:v2.2from
ganiyevuz:patch-1
Jun 17, 2026
Merged

Fix username encoding in PublicKeyCredentialUserEntity#79
mkalioby merged 1 commit into
mkalioby:v2.2from
ganiyevuz:patch-1

Conversation

@ganiyevuz

Copy link
Copy Markdown
Contributor

convert USERNAME_FIELD to string to fix AttributeError at /passkeys/reg/begin/
'int' object has no attribute 'encode' error

@mkalioby

mkalioby commented Jun 9, 2026

Copy link
Copy Markdown
Owner

welcome back @ganiyevuz,

Why username became an int?

@ganiyevuz

Copy link
Copy Markdown
Contributor Author

Its not username its username field like when people use phone number or some kind of non string field as their login method they must use charfield currently if they wont it is giving encode method not found error maybe this is not happening for other but when i use telegram id as their username and use integerfield i got this error.

This is small and probaly not all users face this issue but having extra check is ok

@mkalioby
mkalioby changed the base branch from main to v2.2 June 17, 2026 17:45
@mkalioby
mkalioby merged commit 8fe0821 into mkalioby:v2.2 Jun 17, 2026
9 checks passed
@mkalioby

Copy link
Copy Markdown
Owner

Hello @ganiyevuz,

Got it, It is merged and released as v2.2b2, please check it and it will be released soon.

Thanks for the continuous contributions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants