microg
[com.bKash.merchantapp] microg not showing allow app to read otp even after receiving sms, other bkash app works fine
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.
I tried recently with v0.3.9-250932 and it didn't work. As for v0.3.10 the update is not available on F-droid.
Do you want me to try with beta version?
@ale5000-git
microG v0.3.10 isn't suggested by default on F-Droid but you can select it manually inside the F-Droid app. If it doesn't update on the first attempt, it should work after few attempts.
If possible please update both microG Serrvices and microG Companion.
tried. it's still the same.
there is another (similar) app made by the same developer. otp works there fine
On Fri, Oct 31, 2025, 5:31 PM ale5000 @.***> wrote:
ale5000-git left a comment (microg/GmsCore#3067) https://github.com/microg/GmsCore/issues/3067#issuecomment-3472641021
microG v0.3.10 isn't suggested by default on F-Droid but you can select it manually inside the F-Droid app.
If possible please update both microG Serrvices and microG Companion and then post a logcat of the issue.
— Reply to this email directly, view it on GitHub https://github.com/microg/GmsCore/issues/3067#issuecomment-3472641021, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGXDUIKEGDX7BK6NIBDJYIL32NB77AVCNFSM6AAAAACHH2CX7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINZSGY2DCMBSGE . You are receiving this because you authored the thread.Message ID: @.***>
tried. it's still the same.
there is another (similar) app made by the same developer. otp works there fine …
Could you please post a logcat?
i tried taking log with LogFox but nothing showed up. I guess I will have to try from PC.
And could the sms format be a reason behind this? Apparently the sms has a hash like thing but it's like Hello here your otp xxxxxx:Jdisnsuhshs
i mean colon and hash is together
@ale5000-git here is the logcat from starting the app to receiving the otp and waiting for a few seconds before stopping