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

Check for app updates every 8 hours #7765

Merged
merged 1 commit into from
Feb 16, 2022
Merged

Conversation

neil-marcellini
Copy link
Contributor

Details

Rather than checking for app updates once per hour after the initial check, check once every 8 hours.

Fixed Issues

$ #7643

Tests

  1. Comment out this line so that you get update notifications on your dev environment
  2. npm run desktop
  3. Sign in to the local desktop app
  4. Sign in to the production desktop app
  5. Keep both apps open for 8 hours.
  6. When update notifications pop up for the desktop app hourly, make sure they they don't pop up for the local app.
  • Verify that no errors appear in the JS console

QA Steps

  1. Sign in to the desktop staging app
  2. Sign in to the production desktop app
  3. Keep both apps open for 8 hours.
  4. When update notifications pop up for the desktop app hourly, make sure they they don't pop up for the staging version.
  • Verify that no errors appear in the JS console

Tested On

  • Web
  • Mobile Web
  • Desktop
  • iOS
  • Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

@neil-marcellini neil-marcellini self-assigned this Feb 16, 2022
@neil-marcellini neil-marcellini requested a review from a team as a code owner February 16, 2022 00:50
@MelvinBot MelvinBot requested review from mountiny and removed request for a team February 16, 2022 00:50
@neil-marcellini
Copy link
Contributor Author

I haven't actually tested this yet, but I'm pretty sure it will work since it's a simple change. Tomorrow I will test this and add screenshots to be proper.

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure how much value testing this change thoroughly would bring. The logic is pretty simple here. LGTM!

@neil-marcellini neil-marcellini merged commit 53e8189 into main Feb 16, 2022
@neil-marcellini neil-marcellini deleted the neil-update-frequency branch February 16, 2022 19:30
@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by @neil-marcellini in version: 1.1.40-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

OSBotify commented Mar 1, 2022

🚀 Deployed to production by @yuwenmemon in version: 1.1.40-2 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@flodnv
Copy link
Contributor

flodnv commented Mar 3, 2022

Hmmm. The proposal was about reducing the notifications, not the checking itself.

@mountiny
Copy link
Contributor

mountiny commented Mar 3, 2022

Oh, that is a good point, I have overlooked that during a review @neil-marcellini

@neil-marcellini
Copy link
Contributor Author

neil-marcellini commented Mar 4, 2022

@flodnv
What would be the benefit to checking more often, but notifying only every 8 hours?

@flodnv
Copy link
Contributor

flodnv commented Mar 7, 2022

To clarify, does the app check on startup?

@neil-marcellini
Copy link
Contributor Author

Yes it checks on startup. When init is called on the electron updater it checks for updates here. The behavior is similar for web.

@flodnv
Copy link
Contributor

flodnv commented Mar 7, 2022

I think it's probably fine although it feels a bit weird to knowingly introduce an "improvement" that means that most of our user base will be on an older version for several hours at a time. Perhaps it's ok though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants