LoginUrl not appending query string

[pelguetat]

Hi. I have 2 bots I setup a few months ago and 2 bots I setup last week. I also have successfully setup a login url for the original bots. My problem is that for the new bots, when sending the login url button to users it won't append the authorization data to the query string. It just makes a simple call to my endpoint. I made sure the domains are correct in the bot configuration.
To add to this, for some reason when to login prompt comes up to the user, the request to authorize sending messages is not there, even though it's set to True in the LoginUrl object.

[Bibo-Joshi]

Hi. Can you provide an MWE?

[Bibo-Joshi]

I modified your example slightly, most importantly by adding an endpoint for the login ulr:

import logging

from telegram import Bot, InlineKeyboardButton, InlineKeyboardMarkup, LoginUrl, Update
from telegram.ext import (
    Application,
    CallbackContext,
    CommandHandler,
)
from contextlib import asynccontextmanager

from fastapi import FastAPI, Request, Response
import uvicorn
from http import HTTPStatus

logging.basicConfig(
    format="%(asctime)s - %(name)s - %(levelname)s - %(message)s", level=logging.INFO
)


bot_token1 = "token"
webhook_url_base = "https://domain.tld"

webhook_url_endpoint = webhook_url_base + "/webhook"
login_url_endpoint = webhook_url_base + "/loginurl/"
bot1 = Bot(token=bot_token1)
ptb1 = application = (
    Application.builder()
    .token(bot_token1)
    .read_timeout(7)
    .get_updates_read_timeout(42)
    .build()
)


async def send_login_button(
    update: Update, context: CallbackContext, button_text="Login"
):
    # Create a LoginUrl object
    login_url = LoginUrl(
        url=login_url_endpoint,
        request_write_access=True,
    )

    # Create an InlineKeyboardButton with the LoginUrl
    keyboard = InlineKeyboardMarkup(
        inline_keyboard=[[InlineKeyboardButton(text=button_text, login_url=login_url)]]
    )
    # Send a message with the button
    await context.bot.send_message(
        chat_id=update.effective_chat.id,
        text="Please log in using the button below:",
        reply_markup=keyboard,
    )


async def start(update: Update, context: CallbackContext):
    user_id = update.effective_user.id
    logging.info(f"Handling message from user: {user_id}")

    await send_login_button(update=update, context=context)


@asynccontextmanager
async def lifespan(_: FastAPI):
    await ptb1.bot.setWebhook(webhook_url_endpoint)
    async with ptb1:
        await ptb1.start()
        yield
        await ptb1.stop()


app = FastAPI(lifespan=lifespan)


@app.post("/webhook")
async def receive_update(request: Request):
    update = await request.json()
    logging.info(f"Webhook received data: {update}")

    update = Update.de_json(update, ptb1.bot)
    # Create a dummy CallbackContext

    # Set additional data in the context that can be accessed in handlers
    # context.user_data["bot_personality"] = "boyfriend"
    await ptb1.process_update(update)

    # Add update to the application's update queue
    return Response(status_code=HTTPStatus.OK)


@app.get("/loginurl")
async def receive_update(request: Request):
    logging.info(f"LoginUrl query parameters: {list(request.query_params.keys())}")
    return Response(status_code=HTTPStatus.OK)


ptb1.add_handler(CommandHandler("start", start))

if __name__ == "__main__":

    # In production, run uvicorn with the appropriate settings
    uvicorn.run(app, host="0.0.0.0", port=5000, log_level="info")

Example output:

2024-02-20 17:59:01,979 - httpx - INFO - HTTP Request: POST https://api.telegram.org/bot<TOKEN>/sendMessage "HTTP/1.1 200 OK"
INFO:     192.168.178.24:59374 - "POST /webhook HTTP/1.0" 200 OK
INFO:     192.168.178.24:59388 - "GET /loginurl/?id=...&auth_date=1708448342&hash=c03dafd23ea2e5...f088c63931 HTTP/1.0" 307 Temporary Redirect
2024-02-20 17:59:03,722 - root - INFO - LoginUrl query parameters: ['id', 'first_name', 'last_name', 'username', 'photo_url', 'auth_date', 'hash']

Note that the url parameters can be seen in your browser after you click on the login buttons. If they are not visible there, then they won't be visible on the bot side either - and this is nothing that PTB can control.

This looks good to me. I was also prompted the to authorize sending messages - on the first time that I logged in. If you use the same domain & bot for the login across several projects, then the user will only have to log in once AFAIK.

[pelguetat]

Thanks for the help. It's still not passing the query parameters. Any other ideas as to what might be causing it? I'm losing my mind here.

[Bibo-Joshi]

No, sorry. I suggest to reach out to TG directly (e.g. bugs.telegram.org or GitHub.com/tdlib/telegram-bot-api) as this is not controlled by the Bot API

[pelguetat]

I fixed it. For posterity, it was an issue with my Telegram account. I got a new phone and went to set up the account there, and thought to try again and it worked this time. Thanks for the help by the way.