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

mweb/Desktop - Growl - User does not receive a growl when offline in workspace options #10547

Closed
kbecciv opened this issue Aug 24, 2022 · 15 comments
Assignees
Labels
Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor Improvement Item broken or needs improvement.

Comments

@kbecciv
Copy link

kbecciv commented Aug 24, 2022

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Access staging.new.expensify.com on mweb (Or desktop app)
  2. Sign into a valid account
  3. Tap on Profile icon > Workspace > Reimburse Expenses (Can be any workspace option that should display a growl)
  4. Turn off internet connection
  5. Tap on "View all receipts" while offline

Expected Result:

User expects to receive a growl when offline

Actual Result:

The button does not seem to be responsive, as no growl is received even though it is being pressed.

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Desktop App
  • Mobile Web

Version Number: 1.1.89.0

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers): any

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5702599_User_also_doesnt_receive_growls_on_desktop.mp4
Bug5702599_User_does_not_recieve_a_growl_when_offline.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

@kbecciv kbecciv added the DeployBlockerCash This issue or pull request should block deployment label Aug 24, 2022
@OSBotify
Copy link
Contributor

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

@melvin-bot
Copy link

melvin-bot bot commented Aug 24, 2022

Triggered auto assignment to @bondydaa (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@sketchydroide
Copy link
Contributor

I cannot replicate this one, and there was another similar to this one that could not be replicated

@sketchydroide
Copy link
Contributor

Seems like @luacmartins can't replicate either I'm leaning on not a blocker

@luacmartins luacmartins added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 labels Aug 25, 2022
@bondydaa bondydaa removed their assignment Aug 25, 2022
@bondydaa bondydaa added the Improvement Item broken or needs improvement. label Aug 25, 2022
@bondydaa
Copy link
Contributor

User expects to receive a growl when offline

I think since we're moving toward Brick Road error handling we are getting rid of growls, right?

cc @iwiznia

@bondydaa
Copy link
Contributor

once we figure out if this should be Brick Road or Growl we can probably make it external, will leave as daily until we get more insight.

@bondydaa
Copy link
Contributor

bondydaa commented Aug 25, 2022

discussed here https://expensify.slack.com/archives/C02HWMSMZEC/p1661447438916179

TL:DR yes for now we should have a growl give the user some feedback, even if it's just "you're offline". This should be doable by a contributor so adding that label

From Robert

IIRC, the discussion was that we would have to know prior to that action that the user is Offline and show some sort of indicator that they can’t move forward with that step: be it a growl, or selectively disabling the link/button

@bondydaa bondydaa added the External Added to denote the issue can be worked on by a contributor label Aug 25, 2022
@melvin-bot
Copy link

melvin-bot bot commented Aug 25, 2022

Triggered auto assignment to @dylanexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@melvin-bot
Copy link

melvin-bot bot commented Aug 29, 2022

@dylanexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

@melvin-bot melvin-bot bot added the Overdue label Aug 29, 2022
@dylanexpensify
Copy link
Contributor

reviewing today :)

@melvin-bot melvin-bot bot removed the Overdue label Aug 30, 2022
@dylanexpensify
Copy link
Contributor

So it seems this isn't reproducible. Do we still want to export cc @bondydaa @sketchydroide ?

@sketchydroide
Copy link
Contributor

I think this is not always reproducible, maybe we can ask QA to try again, and see if this is still an issue
@kbecciv can you guys check if this still happens for your guys?

@kbecciv
Copy link
Author

kbecciv commented Aug 30, 2022

@sketchydroide Checking with team, will update you shortly.

@kbecciv
Copy link
Author

kbecciv commented Aug 30, 2022

@sketchydroide Unable to reproduce it for all environments.

@sketchydroide
Copy link
Contributor

thanks, I think we can close for now, if it's an issue we will reopen, it might be that a PR that was needed did not go toghether with another one, or a Web PR was not in Staging at the time of testing, and it was soon after.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor Improvement Item broken or needs improvement.
Projects
None yet
Development

No branches or pull requests

6 participants