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 on 4.2.1 and "broken" account #1582

Closed
rstockm opened this issue Jan 14, 2020 · 3 comments · Fixed by #1585
Closed

Crash on 4.2.1 and "broken" account #1582

rstockm opened this issue Jan 14, 2020 · 3 comments · Fixed by #1585

Comments

@rstockm
Copy link

rstockm commented Jan 14, 2020

Rocket.Chat Version: 2.3.1 via Snap |
NodeJS Version: 8.15.1 - x64 |
MongoDB Version: 3.6.14 |
MongoDB Engine: wiredTiger

I just installed the RocketChat App 4.2.1 on my iPhone 8. It updated flawless from 4.1.0 to my account. I gave a emoticon-feedback on a posting, and the trouble started:

  • the comment didn't show up (this is quite usual, it takes seconds or even minutes)
  • In the overview page it read "no comment"
  • The app crashed a few seconds after.
  • Every attempt to restart the app: immediate crash to Springboard.
  • I deletet the app an logged in again: same behavior.
  • I deleted the app an logged in with a different account: success!! O__o
  • On every other device the first account still works.

What went wrong, and how can I "repair" my first account (I'm admin on my own server, running a Snap install).

@phoenix-schwarz
Copy link

2020-01-16 09 10 27

Ich have the same issue and got this report on my Android phone. I have the same version on iOS as well. The native desktop client works.

@rstockm
Copy link
Author

rstockm commented Jan 16, 2020

Update: my app "repaired itself" to some degree. I can login and use most of the channels. There is still at least one channel wish triggers an instant crash to Springboard. The "posting of doom" which triggers the crash seems to be in a thread. I'm on iOS and "report crashes" is turned on, so you should see the crash report - I just triggered a crash right now.
I updatet to 4.2.2 and can still reproduce the crash.

@rstockm
Copy link
Author

rstockm commented Jan 19, 2020

Just to let you know: Release 4.2.3 from today did not solve my "Posting of doom" Problem above. The app still crashes in one channel/thread. It may be related to a "thread within a thread" situation.
Further findings: the iPad is not affected, just the iPhone app.

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

Successfully merging a pull request may close this issue.

2 participants