Open churik opened 1 month ago
churik
commented
1 month ago https://github.com/user-attachments/assets/12f834d2-e481-4851-8aad-1704babe2353
on @qoqobolo device the error appears for a moment, but she was able to log in afterwards, video attached
pavloburykh
commented
1 month ago I have faced this issue as well on my Android 12, Samsung Galaxy A52 (build - release 2.30)
It appeared after app session was killed after being in the background for a short period of time, i.e.:
I was never able to login that user again although I made many tries.
Parveshdhull
commented
1 month ago I also faced this issue long time ago in one of my account. Related logs and re-frame event: https://github.com/status-im/status-mobile/issues/18103
qfrank
commented
2 weeks ago would be great if we have logs provided @churik
churik
commented
2 weeks ago that was eactly the moment when logging was completely broken in release builds, hopefully logs of Parvesh might help. we'll add logs when we got ones.
churik
commented
2 days ago Well, so :)
Diana was able to reproduce it after upgrade as well, but no logs at all even after she was able to login again and enable them, as it happens BEFORE login. All that we get:
1. Issue Description
<no value>
2. Steps to reproduce
<no value>
3. Attach screenshots that can demo the problem, please
----------------------------------------
App version: 2.30.0 (20240826172533)
OS: ios
Node version:
----------------------------------------
Node Info
id:
ip:
port:
----------------------------------------
Peers
----------------------------------------
Sep 10, 2024, 5:31:04 PM
so I really think https://github.com/status-im/status-mobile/issues/18103 the only logs that we have. Or we cna try to reproduce it if you point me how to get v1 app from the testflight.
qfrank
commented
1 day ago as it happens BEFORE login
I remember we can share logs before login via shake devices -> Share logs(rather than Report a bug) 🤔
I found the UI is different after select option Share logs, for PR build is like this(which seems correct):
but for release build is like this:
is this normal ? @Parveshdhull
qfrank
commented
1 day ago Because the release build disables logs by default... so that's why I see a different UI. I'm curious why it's disabled by default. Is it because of privacy? I thought we should set the error level by default. Privacy makes it hard for us... 😅 @ilmotta
ilmotta
commented
16 hours ago Privacy makes it hard for us... 😅
Oh yes, we work in hard mode in Status.
Because the release build disables logs by default... so that's why I see a different UI. I'm curious why it's disabled by default. Is it because of privacy? I thought we should set the error level by default
@qfrank I don't know the answer. Probably too old at this point for us to reliably answer. I found a commit from 6 years ago that first defined a default log level of "" https://github.com/status-im/status-mobile/commit/8d053b4389a61cb91f83281a7db950c4470ceb3f#diff-4c0bfd9d1eebff16dd8e3afabb50e3e46698f35a597a65f2028e9df721cf110aR37
Our default still is the empty level https://github.com/status-im/status-mobile/blob/babcd96fb625aa843d373ced160d94fd6e54bbd9/src/status_im/config.cljs#L78
Bug Report
Problem
Expected behavior
After some time in the background, it was very hard to login again (for me it was reproducible on the upgraded app). You're trying to enter a password, and you're 100% sure that this is the right one (in my case it was
qwertyasdf) and the app gives you "Incorrect password" error.Sometimes to enter the invalid password and then try again valid helped, but not always (this is on video) At some point, I changed the password and after that I couldn't login at all.
Actual behavior
https://github.com/user-attachments/assets/8c63ace0-dce8-4656-b010-5012f12a2ea3
Reproduction
Unfortunately the issue is random and happened several times for different people.
Additional Information