Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sending special sms during bank app setup fails with code 1 (or code 124 if VoLTE disabled) #299

Open
7 tasks done
Szwendacz99 opened this issue Feb 1, 2025 · 6 comments
Labels
bug Something is not working needs triage Issue is not yet ready for PR authors to take up waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed.

Comments

@Szwendacz99
Copy link

Checklist

  • I can reproduce the bug with the latest version given here.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected app version

1.1.4

Affected Android/Custom ROM version

Android 14

Affected device model

MyPhone N23 Plus

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

  1. Open bank app
  2. Follow first login setup
  3. On login step, when bank require me to send sms with specific content, the Messages app opens properly, with input filled with the required contents, but on send it fails

Expected behavior

the sms is sent correctly

Actual behavior

the message fails to send, allowing me to retry. 2 Toast mesages are shown - one that there is some problem with carrier, and other tells about error code 124. When I enable VoLTE in settings, I am gettind just one Toast with error code 1.

Screenshots/Screen recordings

No response

Additional information

  • Other than that, messaging generally works with other numbers, also when trying to send the same message to other numbers. MMS also works.
  • I used adb to clean a lot of system apps tho, that could potentially be related, but then I don't understand why sending stuff to other numbers work OK.
  • The number from bank app seem like normal phone number, not any special shorter one.
  • I installed some app from Google play store (using Aurora), and that app succeeded, additionally proving that it is rather not related to the installed android and system apps state.
@Szwendacz99 Szwendacz99 added bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Feb 1, 2025
@naveensingh
Copy link
Member

naveensingh commented Feb 1, 2025

Error code 1 is just a generic error but code 124 is a radio interface error (somehow caused by disabling VoLTE):

 
/** Generic failure cause */
public static final int RESULT_ERROR_GENERIC_FAILURE    = 1;

/**
 * A RIL error occurred during the SMS send.
 */
public static final int RESULT_RIL_GENERIC_ERROR = 124;

I installed some app from Google play store (using Aurora), and that app succeeded, additionally proving that it is rather not related to the installed android and system apps state.

Just to clarify, do you mean you installed another messaging app and you were able to send your message using that app?

If not:

@Aga-C Aga-C added question Further information is requested waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. labels Feb 1, 2025
@Szwendacz99
Copy link
Author

I just tested on different phone, and there it seem to work. Weird, considering that different app for messages from Gplay seem to work on the phone where problem occurs. On the other phone, where it work, I have different carrer (another sim card), maybe it is related. I might try later to restore some apps via adb, to see if that helps, but I think I would rather not delete something related to gsm.

@naveensingh naveensingh removed the question Further information is requested label Feb 2, 2025
@naveensingh
Copy link
Member

On the other phone, where it work, I have different carrer (another sim card), maybe it is related.

You can try swapping out the SIM card, that will help confirm if it's a carrier issue.

I might try later to restore some apps via adb, to see if that helps

Let us know how it goes.

@Aga-C
Copy link
Member

Aga-C commented Feb 2, 2025

 I just tested on different phone, and there it seem to work.

Have you downloaded the same Fossify Messages version? Because today has been released 1.1.5 that fixes #294. Try updating the app on your main phone and check again.

@Szwendacz99
Copy link
Author

Szwendacz99 commented Feb 2, 2025

On Fdroid there is still 1.1.4, so definitely I used 1.1.4 on both phones. But then I restored all deleted apps via adb and tested stuff (problem still occured). I also updated the app to 1.1.5 using apk from github tag and I think it worked, but then my small mobile plan run out (I basically had it just for few sms, like this for bank app). At the same time I found out how broken is the mobile-related policy of my bank. So I might return later with conclusion if the newer version really helped, but I need to contact bank, so they fix their stuff lol.

Edit: Fixed my english a bit

@JimmyS83
Copy link

JimmyS83 commented Feb 3, 2025

1.1.5 tested by one SMS and sending through google contact app seems to work fine now. Thanks!

@naveensingh naveensingh added duplicate This issue or pull request already exists bug Something is not working question Further information is requested waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. and removed bug Something is not working waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. needs triage Issue is not yet ready for PR authors to take up duplicate This issue or pull request already exists labels Feb 3, 2025
@naveensingh naveensingh reopened this Feb 3, 2025
@Aga-C Aga-C added needs triage Issue is not yet ready for PR authors to take up and removed question Further information is requested labels Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working needs triage Issue is not yet ready for PR authors to take up waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed.
Projects
None yet
Development

No branches or pull requests

4 participants