Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shards.test fleet is set instead of status.prod after upgrade (1.20.6 => 2.30 => 2.31/2.32) #21835

Open
pavloburykh opened this issue Dec 17, 2024 · 0 comments

Comments

@pavloburykh
Copy link
Contributor

pavloburykh commented Dec 17, 2024

Please, follow the exact upgrade flow described below (1.20.6 => 2.30 => 2.31 or 2.32):

Steps:

  1. Install v1 (1.20.6) Status app
  2. Create/restore user
  3. Upgrade to Status 2.30
  4. Upgrade to Status 2.31 or 2.32
  5. Login the app and check which fleet is enabled (Profile settings - Advanced - fleet)

Expected result: status.prod fleet is enabled

Actual result: shards.test fleet is enabled. User will experience issues related to fetching data (e.g. communities will fail to fetch).

telegram-cloud-document-2-5406616883606610739.mp4

the interesting fact is that upgrading 2.30 =>2.31 or 2.30 => 2.32 will not result in the issue.

i.e. it affects users who initially upgraded from 1.20.6 => 2.30 => and so on.

  • Status version: nightly
  • Operating System: Android, iOS
@pavloburykh pavloburykh changed the title Shards.test fleet is set instead of status.prod after upgrade (1.20.6 => 2.30 => 2.32) Shards.test fleet is set instead of status.prod after upgrade (1.20.6 => 2.30 => 2.31/2.32) Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants