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

[Toast error] illegalStateException #287

Closed
7 tasks done
biopsin opened this issue Jan 23, 2025 · 4 comments · Fixed by #302
Closed
7 tasks done

[Toast error] illegalStateException #287

biopsin opened this issue Jan 23, 2025 · 4 comments · Fixed by #302
Assignees
Labels
bug Something is not working

Comments

@biopsin
Copy link

biopsin commented Jan 23, 2025

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.2, 1.1.3

Affected Android/Custom ROM version

Lineageos-18.1

Affected device model

Sony xperia 1ii

How did you install the app?

GitHub releases, Google play

Steps to reproduce the bug

On recieving MMS from any sender a toast pops up with text :

Error:
java.lang.illegalStateException: Cannot access database on the main thread since it may potentially lock the UI for a long period of time.

however MMS arrives and applicaton seems to work normaly.

Expected behavior

No toast error messages

Actual behavior

Toast error message on recieving MMS

Screenshots/Screen recordings

No response

Additional information

EDIT : Im currently testing a downgrade to 1.1.2 google play version, but same issue here as well

@biopsin biopsin added bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Jan 23, 2025
@biopsin
Copy link
Author

biopsin commented Jan 25, 2025

Adding 1.1.4 from gplay to same issue report.

@naveensingh naveensingh self-assigned this Jan 28, 2025
@Aga-C Aga-C removed the needs triage Issue is not yet ready for PR authors to take up label Jan 31, 2025
naveensingh added a commit that referenced this issue Feb 1, 2025
@naveensingh
Copy link
Member

It would be great if anyone could test out this debug APK here: https://github.com/FossifyOrg/Messages/actions/runs/13089893774/artifacts/2521401317

I can not test MMS messages and this only happens when receiving MMS messages.

@pm-global
Copy link

Just tested this build with a couple incoming MMS images.

No longer get the error message on my Galaxy Note 9 running Android 10.

Thanks!

@naveensingh
Copy link
Member

Thanks! A new version will be released soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants