We've noticed an issue where the Web-A client ignores the choose=users query parameter. I've tested other values for choose, and they are also ignored.
Web-A Client Behavior: Opens the mini-app directly, without displaying a dialog to select a user.
Expected Behavior (Observed in Other Clients): Opens a dialog with a list of users.
Impact:
Our app relies on the selected user ID from the dialog. However, in the Web-A client, we instead receive our bot's ID in Telegram.WebApp.initDataUnsafe.receiver.id.
This issue disrupts our app's functionality. Could you please investigate?
Hello,
We've noticed an issue where the Web-A client ignores the choose=users query parameter. I've tested other values for choose, and they are also ignored.
Example Link:
https://t.me/DurgerKingBot?startattach=test&choose=users
Web-A Client Behavior: Opens the mini-app directly, without displaying a dialog to select a user. Expected Behavior (Observed in Other Clients): Opens a dialog with a list of users.
Impact:
Our app relies on the selected user ID from the dialog. However, in the Web-A client, we instead receive our bot's ID in
Telegram.WebApp.initDataUnsafe.receiver.id
.This issue disrupts our app's functionality. Could you please investigate?
Thank you!