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

Error Code 5 with pic under limit #199

Closed
7 tasks done
Shuggaloaf opened this issue Jul 31, 2024 · 5 comments
Closed
7 tasks done

Error Code 5 with pic under limit #199

Shuggaloaf opened this issue Jul 31, 2024 · 5 comments
Labels
duplicate This issue or pull request already exists

Comments

@Shuggaloaf
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.0.1

Affected Android/Custom ROM version

Android 12

Affected device model

Samsung S10e

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

  1. Add an image under the limit size in settings.
  2. Hit Send
  3. See error

Expected behavior

Pic is sent

Actual behavior

Pic is not sent. Error Code 5

Screenshots/Screen recordings

No response

Additional information

I have had the attachment limit set to 1MB and this has been working for the last week (since I 1st installed). Today I started getting this error. I also tried changing the limit to 2MB and have the same issue.

I did some testing with sending pics of varying sizes. It seems anything over 800KB does get sent. It doesn't matter what the attachment limit size is.

To rule out a change with my carrier, other than checking online I also tried the default messaging app and Textra. Both were able to send all pics without issue.

Because of that, and that this was working yesterday and nothing has changed (no app or phone updates, no setting changes), this is seeming like a bug. Let me know what other info can help.

@Shuggaloaf Shuggaloaf added bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Jul 31, 2024
@Aga-C
Copy link
Member

Aga-C commented Jul 31, 2024

What is the file format of the image you are trying to send?

Also, if you weren't able to send an image with the limit set to 1 MB, changing it to 2 MB doesn't make sense. You should set it to 600 kB or even lower.

@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 Jul 31, 2024
@Shuggaloaf
Copy link
Author

All images are jpg.

I guess you're right with that but since I can send those same images with other 2 other apps I'm guessing it's not related to that anyway (Textra I have set to 2MB w/o issue).

@github-actions github-actions bot removed the waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. label Jul 31, 2024
@Aga-C
Copy link
Member

Aga-C commented Jul 31, 2024

I guess you're right with that but since I can send those same images with other 2 other apps I'm guessing it's not related to that anyway (Textra I have set to 2MB w/o issue).

Have you at least tried changing the limit to any value lower than 1 MB? It will help us to know whether it's a problem with file size limit or something different. Textra isn't a good example here because in the other bug report it was found that Textra compresses images much below the set limit (#45 (comment)).

@Aga-C Aga-C added waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. and removed question Further information is requested labels Jul 31, 2024
@Shuggaloaf
Copy link
Author

Shuggaloaf commented Jul 31, 2024

Ah I see, sorry I misunderstood the need for that test. I just tried 600kb and it did go through.

However something still seems off because this is what T-mobile says about their SMS limits:

All networks restrict the size of MMS. For T-Mobile, the max sending size is 1MB, 3 MB for receiving, and under 3072 x 3072 resolution.

The original size of the image I sent was 818kb and was well below those dimensions.
I also checked with the person I sent the image to when I tested with textra and the size came through unchanged. Not saying I don't believe they would do so with larger pics, but at least with pic sizes under the 1MB limit I have set (and I guess under the carriers 1MB limit?) it seems they are not being resized.

So I guess it boils down to (1) my carrier allows SMS <= 1MB; (2) I can send an 800kb file with Textra and it is received as 800kb (proving the network is allowing this filesize); and (3) I cannot send the same file with Fossify Messenger unless shrinking it.

Is it possible FM is adding some kind of overhead that would kick it above the 1MB limit? (So approx 180kb)

@github-actions github-actions bot removed the waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. label Jul 31, 2024
@naveensingh
Copy link
Member

Isn't this a duplicate of #45?

We should keep 'Error code 5' in one place as it's always about the final MMS size.

@Aga-C Aga-C closed this as not planned Won't fix, can't repro, duplicate, stale Aug 1, 2024
@Aga-C Aga-C added duplicate This issue or pull request already exists and removed bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants