Endless logout on IOS and endless login on Android until app reopeing

[churik]

Bug Report

Problem

CRs are not delivered to the recipient

Expected behavior

can see CR

Actual behavior

no CR

Reproduction

1. Android: create profile > logout > login

FILE.2023-11-14.15.11.18.mp4

2. IOS: create profile > logout

FILE.2023-11-14.15.11.44.mp4

Additional Information

• Status version: release 1.26 RC1
• Operating System: Android, iOS

CR_receiver_Anndroid.zip
CR_sender_IOS.zip

[qfrank]

@churik i can't reproduce Endless logout on IOS on my xs max with this PR , did i miss some steps? cc @pavloburykh

[pavloburykh]

@churik i can't reproduce Endless logout on IOS on my xs max with this PR , did i miss some steps? cc @pavloburykh

@qfrank I am reproducing endless logout on my IOS 16.7, iPhone X using given steps create profile > logout

[qfrank]

relate log for login issue:

1 @ 0x7d403afa14 0x7d403c124c 0x7d403c1229 0x7d403dd304 0x7d403e6978 0x7d41c2ed30 0x7d41c2eccd 0x7d41c2e678 0x7d41c2fb70 0x7d41c2fa44 0x7d41c5f564 0x7d41c3a25c 0x7d403e1644
#\t0x7d403dd303\tsync.runtime_SemacquireMutex+0x23\t\t\t\t\t\t\truntime/sema.go:77
#\t0x7d403e6977\tsync.(*Mutex).lockSlow+0x177\t\t\t\t\t\t\t\tsync/mutex.go:171
#\t0x7d41c2ed2f\tsync.(*Mutex).Lock+0x8f\t\t\t\t\t\t\t\t\tsync/mutex.go:90
#\t0x7d41c2eccc\tgit.luolix.top/status-im/status-go/api.(*GethStatusBackend).ensureWalletDBOpened+0x2c\tgit.luolix.top/status-im/status-go/api/geth_backend.go:419
#\t0x7d41c2e677\tgit.luolix.top/status-im/status-go/api.(*GethStatusBackend).ensureDBsOpened+0x47\t\tgit.luolix.top/status-im/status-go/api/geth_backend.go:357
#\t0x7d41c2fb6f\tgit.luolix.top/status-im/status-go/api.(*GethStatusBackend).loginAccount+0xbf\t\tgit.luolix.top/status-im/status-go/api/geth_backend.go:615
#\t0x7d41c2fa43\tgit.luolix.top/status-im/status-go/api.(*GethStatusBackend).LoginAccount+0x23\t\tgit.luolix.top/status-im/status-go/api/geth_backend.go:591
#\t0x7d41c5f563\tgit.luolix.top/status-im/status-go/mobile.LoginAccount.func1+0x73\t\t\t\tgit.luolix.top/status-im/status-go/mobile/status.go:317
#\t0x7d41c3a25b\tgit.luolix.top/status-im/status-go/api.RunAsync.func1+0x2b\t\t\t\t\tgit.luolix.top/status-im/status-go/api/utils.go:16

relate log for logout issue:

1 @ 0x105352cb4 0x10536452c 0x105364509 0x10537fbd8 0x10538b4b0 0x1061112cc 0x1061a9608 0x1061a8d94 0x106b4ccc0 0x106b4ca84 0x106b66558 0x106b8e06c 0x106b99990 0x106ba1a40 0x10531ac14 0x10531a948 0x1053843f0 0x1053844c4
#\t0x10537fbd7\tsync.runtime_Semacquire+0x27\t\t\t\t\t\t\t\t\t\t/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-go-1.19.9/share/go/src/runtime/sema.go:62
#\t0x10538b4af\tsync.(*WaitGroup).Wait+0x7f\t\t\t\t\t\t\t\t\t\t/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-go-1.19.9/share/go/src/sync/waitgroup.go:139
#\t0x1061112cb\tgit.luolix.top/status-im/status-go/wakuv2.(*Waku).Stop+0x7b\t\t\t\t\t\t\t/private/tmp/nix-build-status-go-develop-fc592ab-ios.drv-0/go/src/github.com/status-im/status-go/wakuv2/waku.go:1303
#\t0x1061a9607\tgit.luolix.top/status-im/status-go/vendor/github.com/ethereum/go-ethereum/node.(*Node).stopServices+0xb7\t/private/tmp/nix-build-status-go-develop-fc592ab-ios.drv-0/go/src/github.com/status-im/status-go/vendor/github.com/ethereum/go-ethereum/node/node.go:298
#\t0x1061a8d93\tgit.luolix.top/status-im/status-go/vendor/github.com/ethereum/go-ethereum/node.(*Node).Close+0x1e3\t\t/private/tmp/nix-build-status-go-develop-fc592ab-ios.drv-0/go/src/github.com/status-im/status-go/vendor/github.com/ethereum/go-ethereum/node/node.go:218
#\t0x106b4ccbf\tgit.luolix.top/status-im/status-go/node.(*StatusNode).stop+0x13f\t\t\t\t\t\t/private/tmp/nix-build-status-go-develop-fc592ab-ios.drv-0/go/src/github.com/status-im/status-go/node/get_status_node.go:460
#\t0x106b4ca83\tgit.luolix.top/status-im/status-go/node.(*StatusNode).Stop+0x83\t\t\t\t\t\t/private/tmp/nix-build-status-go-develop-fc592ab-ios.drv-0/go/src/github.com/status-im/status-go/node/get_status_node.go:446
#\t0x106b66557\tgit.luolix.top/status-im/status-go/api.(*GethStatusBackend).Logout+0x157\t\t\t\t\t/private/tmp/nix-build-status-go-develop-fc592ab-ios.drv-0/go/src/github.com/status-im/status-go/api/geth_backend.go:2191
#\t0x106b8e06b\tgit.luolix.top/status-im/status-go/mobile.Logout+0x6b\t\t\t\t\t\t\t/private/tmp/nix-build-status-go-develop-fc592ab-ios.drv-0/go/src/github.com/status-im/status-go/mobile/status.go:484
#\t0x106b9998f\tmain.proxystatusgo__Logout+0x1f\t\t\t\t\t\t\t\t\t\t/private/tmp/nix-build-status-go-develop-fc592ab-ios.drv-0/gomobile-work/ios/src/gobind/go_statusgomain.go:1203
#\t0x106ba1a3f\t_cgoexp_d7c451f35df0_proxystatusgo__Logout+0x1f\t\t\t\t\t\t\t\t_cgo_gotypes.go:1635
#\t0x10531ac13\truntime.cgocallbackg1+0x243\t\t\t\t\t\t\t\t\t\t/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-go-1.19.9/share/go/src/runtime/cgocall.go:316
#\t0x10531a947\truntime.cgocallbackg+0xd7\t\t\t\t\t\t\t\t\t\t/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-go-1.19.9/share/go/src/runtime/cgocall.go:235
#\t0x1053843ef\truntime.cgocallback+0x9f\t\t\t\t\t\t\t\t\t\t/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-go-1.19.9/share/go/src/runtime/asm_arm64.s:1094

[qfrank]

all the goroutines:
android-login-stuck-goroutines.log
ios-logout-stuck-goroutines.log

above logs are generated based on this PR

original logs:
Android-Status.log.zip
Ios-Status.log.zip

[qfrank]

Hi @churik , feel free to close this issue when it's not reproducable anymore 🙂

Oh, we should wait and cherry pick commits from this PR into release/0.171.x ? @cammellos

[cammellos]

@qfrank we reverted commits on release already, so I think it's fine

[pavloburykh]

Since we have reverted changes only in release go branch, I propose to keep this issue opened until it is fixed in status - go develop, cause it is still there.

[churik]

It should be fixed in status-go already, but version is not upgraded here yet due to other issues, so I'd agree with @pavloburykh

[pavloburykh]

It should be fixed in status-go already, but version is not upgraded here yet due to other issues, so I'd agree with @pavloburykh

Thank you! I have missed that we already have the fix from Richard for this issue.

[churik]

It should be fixed on latest status-go develop, reopen if it is still the case