Error when creating an account on e2e build

[yevh-berdnyk]

Bug Report

Problem

Sometimes when creating an account we get a popup with error:

Expected behavior

No error

Actual behavior

Please shake your phone to report this error... is shown

Reproduction

1. Create a new account

Additional Information

• Status version: nightly
• Operating System: Android

Logs: logcat_shake_the_phone_error.log

[qfrank]

the version seems old in the screenshot you provided? @yevh-berdnyk

I can't find the usage of "start-using-status" in the cljs file on the latest develop branch. Am I missing something? @Parveshdhull

[Parveshdhull]

Yes, the screenshot is old, but I also encountered this error recently, just two days ago. Status-debug-logs.zip

Note: In my case, I might have installed the wrong build while working on the syncing fallback flow, so the logs may not be very helpful and error might have been expected.

[Parveshdhull]

Ok, as per logs shared by @yevh-berdnyk

07-17 19:12:04.124 24559 24667 E ReactNativeJS: 'An error occured while handling the re-frame event:', '[:visibility-status-updates/visibility-status-option-pressed 1]', '\n', 'Within the', ':visibility-status-updates/visibility-status-option-pressed', 'event handler function.'

I removed this call in https://github.com/status-im/status-mobile/pull/21068, so this issue should be fixed

[Parveshdhull]

@yevh-berdnyk @churik are you still facing this issue?

[Parveshdhull]

I removed this call in https://github.com/status-im/status-mobile/pull/21068, so this issue should be fixed

But in my case, error is

'An error occured while handling the re-frame event:', '[:push-notifications/switch false]', '\n', 'Within the', ':push-notifications/switch', 'event handler function.'

[Parveshdhull]

So most probably, problem is with multiaccounts.update/multiaccount-update. As both functions are using this. So we trying to update an no existing multiaccount, and this is causing the crash.

[Parveshdhull]

Ok, real error in my case

node.login error failed to start node: failed to apply migrations: failed to apply status-go/protocol migrations: failed to migrate: file does not exist

[Parveshdhull]

node.login error failed to start node: failed to apply migrations: failed to apply status-go/protocol migrations: failed to migrate: file does not exist

But as I was working on seed phrase fallback and trying different builds, this probably is expected in my case. So if no one else faces this issue, we can close it?

[yevh-berdnyk]

@yevh-berdnyk @churik are you still facing this issue?

Yes, a lot of. For example, here are the logs from Sep 19 nightly build: requests.log geth.log The pop-up appeared when creating a user

[Parveshdhull]

thank you @yevh-berdnyk for confirming. Do you access to Status.log file

[yevh-berdnyk]

thank you @yevh-berdnyk for confirming. Do you access to Status.log file

Not for now. We gather geth and requests logs by script, if you need it, I can add gathering Status.log as well