Curated communities are not fetched

[pavloburykh]

Steps:

1. Create/restore an account
2. Open Discover communities screen
3. See if Curated communities are fetched

Actual result: Curated communities are not fetched

Status-debug-logs (79).zip

telegram-cloud-document-2-5357306334016451381.mp4

Additional Information

• Status version: nightly
• Operating System: Android, iOS

[churik]

So on desktop:

• when test mode is enabled: https://community-dapp-git-review-status-im-web.vercel.app/directory
• if testnet is not enabled it should reflect: https://curate.status.app/directory

I'm not sure we're aligned on mobile

[ajayesivan]

I checked the last desktop nightly I got from here: https://ci.status.im/job/status-desktop/job/nightly/

Mainnet:

Testnet:

[ajayesivan]

status-go api we use to fetch communities is giving nothing.
API: CuratedCommunities
Response:

{:contractCommunities nil, :contractFeaturedCommunities nil, :communities {}, :unknownCommunities nil}

[ajayesivan]

We are showing the loading screen when the curated communities list is empty:

status-mobile/src/status_im2/contexts/communities/discover/view.cljs

Lines 154 to 157 in abbf29d

	[:<>
	[rn/view {:margin-bottom 16} [quo/community-card-view-item {:loading? true}]]
	[rn/view {:margin-bottom 16} [quo/community-card-view-item {:loading? true}]]
	[quo/community-card-view-item {:loading? true}]])])

[ajayesivan]

In mobile there is no design for empty discover screen: https://www.figma.com/file/h9wo4GipgZURbqqr1vShFN/Communities-for-Mobile?type=design&node-id=7202%3A475069&mode=design&t=7DEoalWujv2AG993-1

[ajayesivan]

So on desktop:

• when test mode is enabled: https://community-dapp-git-review-status-im-web.vercel.app/directory
• if testnet is not enabled it should reflect: https://curate.status.app/directory

I'm not sure we're aligned on mobile

This is what I see in the links you shared,
https://community-dapp-git-review-status-im-web.vercel.app/directory:

https://curate.status.app/directory:

@churik Is it expected to load the lists displayed in these links onto the discover screens?

[ajayesivan]

The Mainnet Community Directory Curation is currently empty and we don't have an empty variant for the discover screen, which is why the loading screen is displayed in this scenario.

[ajayesivan]

• Even in testnet status-go thinks the app is running in mainnet, m.settings.GetTestNetworksEnabled() - returns false - when running with mobile.
• When I forced the code to fetch testnet communities it return one community public key but status-go fails to fetch the corresponding community data.

I tried importing the community with the public key on desktop and it returning nothing, see the screenshot below

[ajayesivan]

I was looking at the wrong place 🥲. In order to get communities on the test network we need to switch to status.test fleet.

Status App -> Settings -> Advanced -> Fleet -> status.test

[ajayesivan]

When we are on testnet & status.test fleet atm there is only one community in the curated communities list:

[pavloburykh]

Hey @ajayesivan

I have checked status.test on mobile and curated community still not fetched for me

[pavloburykh]

So, as far as I understand, we are not able to fetch community on Mainnet as the The Mainnet Community Directory Curation is currently empty as you mentioned above.

At the same community is not fetched on testnet (on mobile) despite there is 1 community that should be fetched.

Could it be the reason that mobile is looking at the wrong endpoints?

[ajayesivan]

@pavloburykh, on mobile there is some issue with testnet or test fleet. It definitely needs a fix, I will ping you once it's ready for testing.

I was adding all my findings here.

[pavloburykh]

We can ask felicio to add some community to Mainnet Community Directory Curation and see if it will be fetched on mobile. But I have an assumption that it will not be fetched.

[pavloburykh]

@pavloburykh, on mobile there is some issue with testnet or test fleet. It definitely needs a fix, I will ping you once it's ready for testing.

I was adding all my findings here.

got it. Thank you for your investigation @ajayesivan

[ilmotta]

@pavloburykh, should we move this issue to release 1.27?

[pavloburykh]

@pavloburykh, should we move this issue to release 1.27?

Yes. I have moved it to 1.27. Thanks @ilmotta