frank

Results 91 comments of frank

Sometimes after app has been shut down automatically (app was stopped by OS) you're not able to login again or it logins randomly even if you enter a password right

> 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...

Sometimes after app has been shut down automatically (app was stopped by OS) you're not able to login again or it logins randomly even if you enter a password right

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...

Sometimes after app has been shut down automatically (app was stopped by OS) you're not able to login again or it logins randomly even if you enter a password right

> Unfortunately logs are not very useful. We do see lots of instances in `Status.log` of: > > ``` > node.login error failed to open database: failed to set `journal_mode`...

Sometimes after app has been shut down automatically (app was stopped by OS) you're not able to login again or it logins randomly even if you enter a password right

> Unfortunately logs are not very useful. We do see lots of instances in `Status.log` of: > > ``` > node.login error failed to open database: failed to set `journal_mode`...

Sometimes after app has been shut down automatically (app was stopped by OS) you're not able to login again or it logins randomly even if you enter a password right

> not sure what we can do here, but it is amazing to have this info thank you [@3esmit](https://github.com/3esmit) > > cc [@qfrank](https://github.com/qfrank) [@ilmotta](https://github.com/ilmotta) the geth.log @3esmit provided is very...

Sometimes after app has been shut down automatically (app was stopped by OS) you're not able to login again or it logins randomly even if you enter a password right

For decrypting the database, pls see [ExportUnencryptedDatabase](https://github.com/status-im/status-go/blob/78da423569f4b9c5ab7b640691ecb51185225ef4/api/geth_backend.go#L944), I have reproduced one of your issue, I'm fixing @3esmit

retry sending specific messages

thanks to @osmaczko , leave chat history with @osmaczko here as reference later cc @cammellos : Hi Patryk, maybe you know something about this: I'm struggling with `SendMessageToControlNode` , it...

retry sending specific messages

You may noticed `messenger_raw_message_resend_test.go` is placed in package `api`, this looks like a mess, however, if i moved it into package `protocol`, it would trigger `import cycle` issue (it's about...

retry sending specific messages

When run `TestMessengerRawMessageResendTestSuite/TestMessageSent` locally for 100 times, there is a possible to get following error: ``` Error: Received unexpected error: MessengerResponse data not received Test: TestMessengerRawMessageResendTestSuite/TestMessageSent ``` relate test code:...

retry sending specific messages

> When run `TestMessengerRawMessageResendTestSuite/TestMessageSent` locally for 100 times, there is a possible to get following error: > > ``` > Error: Received unexpected error: > MessengerResponse data not received >...