[Bug]: get_user_id interface does not work properly #785

New Issue

OVERLORD · 2026-02-04T21:19:54+03:00

OVERLORD commented

2026-02-04 21:19:54 +03:00

Originally created by @shesio on GitHub (Aug 19, 2025).

Where is the problem occurring?

None

What browsers are you seeing the problem on?

No response

Current behavior

I use this API to get a certain user information is a prompt:[Bug]: { "code": "E_MISSING_OR_INVALID_PARAMS", "problems": [ "Invalid "id":\n · Value ('1580458189751583830') did not match the configured regular expression (//^[1-9][0-9]*$/|^me$/)" ], "message": "The server could not fulfill this request (GET /api/users/1580458189751583830) due to 1 missing or invalid parameter." }

Desired behavior

No response

Steps to reproduce

This problem exists in the latest 2.0.0-rc.3 version

Other information

No response

Originally created by @shesio on GitHub (Aug 19, 2025). ### Where is the problem occurring? None ### What browsers are you seeing the problem on? _No response_ ### Current behavior I use this API to get a certain user information is a prompt:[Bug]: { "code": "E_MISSING_OR_INVALID_PARAMS", "problems": [ "Invalid \"id\":\n · Value ('1580458189751583830') did not match the configured regular expression (/\/^[1-9][0-9]*$\/|^me$/)" ], "message": "The server could not fulfill this request (`GET /api/users/1580458189751583830`) due to 1 missing or invalid parameter." } ### Desired behavior _No response_ ### Steps to reproduce This problem exists in the latest 2.0.0-rc.3 version ### Other information _No response_

OVERLORD added the bug label 2026-02-04 21:19:54 +03:00

OVERLORD closed this issue

2026-02-04 21:19:57 +03:00

OVERLORD commented

2026-02-04 21:20:01 +03:00

@meltyshev commented on GitHub (Aug 19, 2025):

Hey! Thanks for reporting this. I was able to reproduce it and already working on a fix.

@meltyshev commented on GitHub (Aug 19, 2025): Hey! Thanks for reporting this. I was able to reproduce it and already working on a fix.

OVERLORD commented

2026-02-04 21:20:06 +03:00

@meltyshev commented on GitHub (Aug 19, 2025):

Fixed 🙂 We'll try to release the final v2 version at the beginning of September.