Contact person: Business Client

Phone:Show

Email:Show

Location: Pune, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Project: Fix Telegram Bot Error & Add Error-Forwarding Logic

Description:
I have an existing Telegram bot built using Python (Telethon + Pyrogram + python-telegram-bot).
The bot’s main flow is:

User sends an APK file to Bot A (my bot).

Bot A forwards the APK to an incoming channel.

The incoming channel automatically forwards the file to my Protect Bot (encryption bot).

Protect Bot returns the signed APK → this must automatically be forwarded to an outgoing channel.

The outgoing channel then forwards the signed APK back to the correct user who originally sent it.

What needs to be fixed / added:

There’s an AttributeError ('NoneType' object has no attribute 'on') that appears around the Telethon event registration; this must be corrected.

Add a small logic block to detect and forward error messages from the Protect Bot:

If Protect Bot sends an error (e.g. “already encrypted”, “could not be processed”), forward that exact text both to the outgoing channel and to the user who submitted the file.

If Protect Bot sends a normal signed APK file, forward it normally to the outgoing channel and then back to the user.

Ensure queue handling and file-forwarding logic still work properly.

Deliverables:

Clean, working [login to view URL] file (or equivalent) with:

Properly registered Telethon handlers

Working error-detection logic

Correct message forwarding path (user → incoming → Protect Bot → outgoing → user)

No duplicate or redundant handlers

Tested and verified in real Telegram environment.

Tech Stack:
Python 3.10+, Telethon, Pyrogram, python-telegram-bot, asyncio

Notes:
The fix is small and focused—just to repair the handler registration error and add the correct conditional forwarding for error messages." (client-provided description)