Store nodes are not available on IOS #19736

pavloburykh · 2024-04-19T13:24:43Z

Regression of #19564 cc @siddarthkay
Tested on IOS 16.7.7, iPhone 10

Steps:

Login Status on IOS
Check if store node is found

Actual result: Store nodes are not found on IOS. Unable to fetch communities / restore data, etc.

logs (33).zip

siddarthkay · 2024-04-19T13:26:39Z

@pavloburykh : does this happen only on iOS? Could you pls check if this happens on Android too?

siddarthkay · 2024-04-19T14:22:03Z

As discussed @jo-mut will take this over

pavloburykh · 2024-04-19T14:31:35Z

@pavloburykh : does this happen only on iOS? Could you pls check if this happens on Android too?

I am not reproducing on Android, that's why I mentioned in the issue that this is IOS only.

pavloburykh · 2024-04-23T10:37:10Z

@jo-mut @siddarthkay hey guys! Curious if there are any updates on this? It kinda blocks us from testing some features (which require connection to store node) on IOS. Maybe we should think about reverting changes in case it is not an easy fix and requires more time for investigation?

jo-mut · 2024-04-23T10:40:37Z

@pavloburykh we may need sometime to investigate it, we are looking into it, we will give an update in the afternoon

pavloburykh · 2024-04-23T10:41:52Z

@pavloburykh we may need sometime to investigate it, we are looking into it, we will give an update in the afternoon

Great! Thank you @jo-mut!

jo-mut · 2024-04-23T14:12:02Z

@pavloburykh : does this happen only on iOS? Could you pls check if this happens on Android too?

I am actually reproducing this on Android too, seems not to be ios only

INFO [04-23|14:11:00.423|github.com/status-im/status-go/protocol/messenger_mailserver.go:834]                                               synced topic                             mailserverID=store-01.do-ams3.shards.test chatIDs=[] fromString=2024-03-23T14:11:00Z toString=2024-04-23T14:11:01Z topic=[0x9dd744bf] from=1,711,203,060 to=1,713,881,461
INFO [04-23|14:11:00.423|github.com/status-im/status-go/protocol/messenger_store_node_request_manager.go:346]                               request finished                         requestID="{RequestType:0 DataID:0x033a350ed1b0de3870a3905d054f7b43af48fe0b809a1ec4bccb2df710f94512cb}" communityFound=false contactFound=false shardFound=false
WARN [04-23|14:11:00.561|github.com/status-im/status-go/vendor/github.com/ethereum/go-ethereum/rpc/handler.go:305]                          Served wakuext_communityUpdateLastOpenedAt reqid=39 duration="973.177µs" err="community not found"
INFO [04-23|14:11:00.885|github.com/status-im/status-go/vendor/github.com/waku-org/go-waku/waku/v2/node/connectedness.go:90]                peer disconnected                        peer=16Uiu2HAkw3d2VhXuEhTy7DD1GYWSF9pHD18MadEfyyK295SHW6sN
ERROR[04-23|14:11:04.082|github.com/status-im/status-go/vendor/go.uber.org/zap/sugar.go:222]                                                failed to resolve local interface addresses error="route ip+net: netlinkrib: permission denied"
ERROR[04-23|14:11:04.964|github.com/status-im/status-go/vendor/go.uber.org/zap/sugar.go:222]                                                failed to resolve local interface addresses error="route ip+net: netlinkrib: permission denied"
INFO [04-23|14:11:04.966|github.com/status-im/status-go/vendor/github.com/waku-org/go-waku/waku/v2/node/wakunode2.go:334]                   listening addresses update received      multiaddr="[/dns4/boot-01.ac-cn-hongkong-c.shards.test.status.im/tcp/30303/p2p/16Uiu2HAmGwcE8v7gmJNEWFtZtojYpPMTHy2jBLL6xRk33qgDxFWX/p2p-circuit/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y /dns4/boot-01.ac-cn-hongkong-c.shards.test.status.im/tcp/443/wss/p2p/16Uiu2HAmGwcE8v7gmJNEWFtZtojYpPMTHy2jBLL6xRk33qgDxFWX/p2p-circuit/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y /ip4/127.0.0.1/tcp/40603/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y /ip4/8.218.23.76/tcp/30303/p2p/16Uiu2HAmGwcE8v7gmJNEWFtZtojYpPMTHy2jBLL6xRk33qgDxFWX/p2p-circuit/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y]"
ERROR[04-23|14:11:05.012|github.com/status-im/status-go/vendor/go.uber.org/zap/sugar.go:222]                                                failed to resolve local interface addresses error="route ip+net: netlinkrib: permission denied"
INFO [04-23|14:11:05.014|github.com/status-im/status-go/vendor/github.com/waku-org/go-waku/waku/v2/node/wakunode2.go:334]                   listening addresses update received      multiaddr="[/dns4/store-01.do-ams3.shards.test.status.im/tcp/30303/p2p/16Uiu2HAmAUdrQ3uwzuE4Gy4D56hX6uLKEeerJAnhKEHZ3DxF1EfT/p2p-circuit/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y /dns4/store-01.do-ams3.shards.test.status.im/tcp/443/wss/p2p/16Uiu2HAmAUdrQ3uwzuE4Gy4D56hX6uLKEeerJAnhKEHZ3DxF1EfT/p2p-circuit/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y /ip4/127.0.0.1/tcp/40603/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y /ip4/8.218.23.76/tcp/30303/p2p/16Uiu2HAmGwcE8v7gmJNEWFtZtojYpPMTHy2jBLL6xRk33qgDxFWX/p2p-circuit/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y /dns4/boot-01.ac-cn-hongkong-c.shards.test.status.im/tcp/30303/p2p/16Uiu2HAmGwcE8v7gmJNEWFtZtojYpPMTHy2jBLL6xRk33qgDxFWX/p2p-circuit/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y /dns4/boot-01.ac-cn-hongkong-c.shards.test.status.im/tcp/443/wss/p2p/16Uiu2HAmGwcE8v7gmJNEWFtZtojYpPMTHy2jBLL6xRk33qgDxFWX/p2p-circuit/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y /dns4/store-01.do-ams3.shards.test.statusim.net/tcp/30303/p2p/16Uiu2HAmAUdrQ3uwzuE4Gy4D56hX6uLKEeerJAnhKEHZ3DxF1EfT/p2p-circuit/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y /ip4/159.223.242.94/tcp/30303/p2p/16Uiu2HAmAUdrQ3uwzuE4Gy4D56hX6uLKEeerJAnhKEHZ3DxF1EfT/p2p-circuit/p2p/16Uiu2HAkvbFbom7Zy1ECxdJD6fnFLmPi1yBPp9rdioEvN8LT4c4y]"

pavloburykh · 2024-04-23T19:42:03Z

I am actually reproducing this on Android too, seems not to be ios only

Hi @jo-mut.

The fact that you are unable to fetch community does not mean you are facing the issue which is described here. Could you please provide me a link to community you are trying to fetch?

The reason why community is not fetched for you might be the following:

Community you are trying to fetch is outdated (control node has been offline more than 30 days.). Try creating a new community.
Recently we had troubles with fetching token gated communities which have minted tokens or set permissions on Sepolia. This was due to problems with Sepolia network (sepolia assets have not been fetched as well). But I am not reproducing this issue now.

Unable to fetch communities (as well as unable to restore backed upa data) is not the bug which is described in this issue but only one of the symptoms of the problem.

The main problem is unable to connect to store node (this is actually described in issue description).

Have you checked if your Android device is connected to store node?

In order to check if your device is connected to store node you need to go to Profile - Legacy settings - Sync settings - Status nodes. Check if connected store node is displayed in Status nodes.

In my case it is empty for IOS and displayed on Android (see screenshots below).

IOS:

Android:

Also, if you check IOS geth log which I have attached to this issue (in the description) you will see the following:

INFO [04-19|13:18:51.256|github.com/status-im/status-go/protocol/messenger_mailserver_cycle.go:283]                                         connecting error                         err="lookup store-02.gc-us-central1-a.shards.test.statusim.net on [::1]:53: read udp [::1]:55417->[::1]:53: read: connection refused"
INFO [04-19|13:18:51.256|github.com/status-im/status-go/protocol/messenger_mailserver_cycle.go:283]                                         connecting error                         err="lookup store-01.ac-cn-hongkong-c.shards.test.statusim.net on [::1]:53: read udp [::1]:63509->[::1]:53: read: connection refused"
INFO [04-19|13:18:51.256|github.com/status-im/status-go/protocol/messenger_mailserver_cycle.go:283]                                         connecting error                         err="lookup store-02.ac-cn-hongkong-c.shards.test.statusim.net on [::1]:53: read udp [::1]:57690->[::1]:53: read: connection refused"
INFO [04-19|13:18:51.256|github.com/status-im/status-go/protocol/messenger_mailserver_cycle.go:283]                                         connecting error                         err="lookup store-01.do-ams3.shards.test.statusim.net on [::1]:53: read udp [::1]:57641->[::1]:53: read: connection refused"
INFO [04-19|13:18:51.256|github.com/status-im/status-go/protocol/messenger_mailserver_cycle.go:283]                                         connecting error                         err="lookup store-02.do-ams3.shards.test.statusim.net on [::1]:53: read udp [::1]:53965->[::1]:53: read: connection refused"
INFO [04-19|13:18:51.256|github.com/status-im/status-go/protocol/messenger_mailserver_cycle.go:283]                                         connecting error                         err="lookup store-01.gc-us-central1-a.shards.test.statusim.net on [::1]:53: read udp [::1]:53716->[::1]:53: read: connection refused"
WARN [04-19|13:18:51.256|github.com/status-im/status-go/protocol/messenger_mailserver_cycle.go:290]                                         No mailservers available

This means the app is unable to connect to mailservers. And it happens to me only on IOS.

siddarthkay · 2024-04-25T12:38:27Z

@pavloburykh : #19798 should fix this issue.

fixes #19736 Corresponding go PR status-im/status-go#5093 This commit fixes DNS resolution inside status-go by forcing pure go resolver at build time. Reference -> https://pkg.go.dev/net#hdr-Name_Resolution Store nodes must be available on Android & iOS app. - Android - iOS status: ready

status-im/status-go@90b18d4...b124e2b fixes #19736 Corresponding go PR status-im/status-go#5093 This commit fixes DNS resolution inside status-go by forcing pure go resolver at build time. Reference -> https://pkg.go.dev/net#hdr-Name_Resolution Store nodes must be available on Android & iOS app. - Android - iOS status: ready

pavloburykh added ios high-priority E:Mobile Bug MVP [no-crew] issue 2.29 labels Apr 19, 2024

pavloburykh mentioned this issue Apr 19, 2024

Display private permissions only when the requirements are met #19675

Merged

siddarthkay assigned siddarthkay and jo-mut and unassigned siddarthkay Apr 19, 2024

mariia-skrypnyk mentioned this issue Apr 24, 2024

fix: community permission context not passing community-id #19669

Merged

jo-mut mentioned this issue Apr 24, 2024

fix: store node are not available on ios #19785

Closed

pavloburykh mentioned this issue Apr 24, 2024

fix alert banner issues #19773

Merged

siddarthkay mentioned this issue Apr 25, 2024

fix dns resolution issue for iOS #19798

Merged

qoqobolo assigned siddarthkay and unassigned jo-mut Apr 26, 2024

siddarthkay closed this as completed in #19798 Apr 26, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Store nodes are not available on IOS #19736

Store nodes are not available on IOS #19736

pavloburykh commented Apr 19, 2024

siddarthkay commented Apr 19, 2024 •

edited

siddarthkay commented Apr 19, 2024

pavloburykh commented Apr 19, 2024

pavloburykh commented Apr 23, 2024 •

edited

jo-mut commented Apr 23, 2024

pavloburykh commented Apr 23, 2024

jo-mut commented Apr 23, 2024 •

edited

pavloburykh commented Apr 23, 2024 •

edited

siddarthkay commented Apr 25, 2024

Store nodes are not available on IOS #19736

Store nodes are not available on IOS #19736

Comments

pavloburykh commented Apr 19, 2024

siddarthkay commented Apr 19, 2024 • edited

siddarthkay commented Apr 19, 2024

pavloburykh commented Apr 19, 2024

pavloburykh commented Apr 23, 2024 • edited

jo-mut commented Apr 23, 2024

pavloburykh commented Apr 23, 2024

jo-mut commented Apr 23, 2024 • edited

pavloburykh commented Apr 23, 2024 • edited

siddarthkay commented Apr 25, 2024

siddarthkay commented Apr 19, 2024 •

edited

pavloburykh commented Apr 23, 2024 •

edited

jo-mut commented Apr 23, 2024 •

edited

pavloburykh commented Apr 23, 2024 •

edited