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

Crash when loading conversations on Android 10 #3117

Closed
Xitee1 opened this issue Jun 23, 2023 · 4 comments
Closed

Crash when loading conversations on Android 10 #3117

Xitee1 opened this issue Jun 23, 2023 · 4 comments
Labels
0. Needs triage bug Something isn't working

Comments

@Xitee1
Copy link

Xitee1 commented Jun 23, 2023

Steps to reproduce

  1. Install and setup Nextcloud Talk on an Samsung Galaxy S9+ running Android 10
  2. Try to open a conversation
  3. Chat is loading
  4. After 1-2 secs of loading, the app crashes and restarts into the conversation overview (Before 17.0.0 it crashed the App completely if I remember correctly)

Expected behaviour

Chat loads and I can read the messages

Actual behaviour

I'm back in the conversation overview and unable to open a conversation

Device brand and model

Samsung Galaxy S9+

Android version

10

Nextcloud Talk app version

17.0.0

Nextcloud server version

Nextcloud Hub 3 (25.0.3)

Talk version

15.0.6

Custom Signaling server configured

No

Custom TURN server configured

Yes

Custom STUN server configured

Yes

Android logs

talk_crash_log.log

Server log

No response

Additional information

My phone is rooted with Magisk if that matters.

My nextcloud is running in an docker container with a slightly modified official image.
coTurn is also running in an docker container.

All other things and calls do work fine if someone calls me. I also managed to create a call in the conversation by clicking really fast on the call icon before the chat loads.

I don't think it is related to #3099 because I also have this issue in previous versions. In version 13.x (or even 14.x?) it works as expected (however of course is outdated).

It works on all other phones I have tested. Only my Galaxy S9+ is affected. Maybe an issue with Android 10? The other phones are running Android 12+.

@Xitee1 Xitee1 added 0. Needs triage bug Something isn't working labels Jun 23, 2023
@Xitee1
Copy link
Author

Xitee1 commented Jun 24, 2023

I've built the project and found out it is working in 17.10.0 Alpha 08.
Still weird that it works on other Android 10 phones (Found one and tested it there) but now it works on my main phone too.

If someone has the same issue, I'll attach the APK so you don't have to build the App or wait for the next release.

--
Had to upload the file to google drive because of Github's 25MB limit: https://drive.google.com/file/d/1Vg66x8Xcshp1SatWx5-bSMn8Shq9IXra/view?usp=sharing

@Xitee1 Xitee1 closed this as completed Jun 24, 2023
@mahibi
Copy link
Collaborator

mahibi commented Jun 26, 2023

it's most probably #3099

@Xitee1
Copy link
Author

Xitee1 commented Jun 26, 2023

Ok, maybe it has fixed my issue too.
But it's not the same cause because I don't have the OpenAI app, I've also had the issue with 15.x and 16.x (not only after 17.0.0) and the issue occured only on 1 of 6 phones I've tested.

But whatever it was, it is fixed now 😄

@mahibi
Copy link
Collaborator

mahibi commented Jun 26, 2023

the problem might be that too much data is passed via intents, so this could lead to crashed depending on server configs (defines how much data is passed) and android versions/devices (how much data can be handled).

I'm not aware that other configs other than OpenAI create so "big" data, but who knows.
A solution will be #3122 which will avoid passing too much data via intents

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants