[com.bKash.merchantapp] microg not showing allow app to read otp even after receiving sms, other bkash app works fine
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: bKash Merchant
Package id: com.bKash.merchantapp
Describe the bug
App sends OTP with hash or whatever, but there's no "Allow app to read message" popup
To Reproduce
Steps to reproduce the behavior:
- Go to app
- Enter number and let it send otp (Bangladeshi IP needed, android vpns will fail)
- otp will come but no allow to read message popup from microg
- See error
Expected behavior
It will show the allow app to read following message popup (sms retriever api)
Screenshots
N/A
System
Android Version: 14
Custom ROM: LineageOS 21 with microg (microg LoS)
microG
microG Core version: i don't see any app named core in my app list, but microG Services is 0.3.7.250932
microG Self-Check results: All ticked except "permission to find accounts on the device" and "permission to interact with work profile"
clicking permission to find accounts on the device doesn't do anything
Additional context
Add any other context about the problem here.
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
No source files or tests are identified. First reproduce the bKash Merchant OTP flow on Android 14 with microG Services, then trace the Android SMS Retriever handling and compare it with the expected permission popup. Done means the popup appears after the OTP SMS is received, without breaking the working flow in other bKash apps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100