[<org.telegram.messenger>] <An internal error occurred. Please try again later... Unable to send SMS. Please try again later.>
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Affected app
Name: [Telegram]
Package id: [org.telegram.messenger]
Describe the bug
I installed Telegram using Aurora Store on LineageOS for microG (fresh install).
I entered the phone number with the country code.
But errors appeared
To Reproduce
Steps to reproduce the behavior:
- Open Telegram app
- Click on Start Messaging.
- Fill in the country code
- Enter phone number
Expected behavior
Telegram sends a verification code via SMS.
Screenshots
System
Android Version: [13]
Custom ROM: [LineageOS for microG 20]
microG
microG Core version: [0.3.0.233515]
microG Self-Check results: [All ticked]
Additional context
Google device registration: On.
Cloud Messaging: On.
It looks like Telegram actually sends verification SMS.
But the verification code does not appear when using microG.
I have confirmed it when I installed the official LineageOS with MindtheGApps.
Lots of verification codes appeared when I logged into Telegram.
The verification code is what I requested when using microG.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source file or test; begin by reproducing Telegram verification on the listed LineageOS for microG and microG versions, then trace the SMS or Cloud Messaging path used during sign-in. Compare the behavior with official LineageOS and MindTheGApps; done means Telegram verification codes arrive under microG as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100