You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version Number: v9.0.17-0 Reproducible in staging?: Y Reproducible in production?: N Email or phone of affected tester (no customers):abebemiherat@gmail.com Issue reported by: Applause Internal Team
Action Performed:
Sign in to the new dot.
Click on Ctrl + D.
Observe that the modal appears.
Attempt to toggle the 'User Profile' and notice that it does not work.
Expected Result:
The user should be able to toggle the 'User Profile'.
Actual Result:
The user is unable to toggle the 'User Profile'.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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:
Identify the pull request that introduced this issue and revert it.
We enabled this toggle in dev mode, but to enable it in prod (staging and prod) you'll need to add 'Document-Policy': 'js-profiling' header to html response.
I don't have permissions to deploy so I can not fix it, but if someone can shed some light on where and how the app is hosted (is it AWS S3?) then I can co-operate with that person and together we can fix that 🤞
Hey @thienlnam any progress here please? I see you added the Infra label - what's the intention for that to assign a specific person/group so that we can move this forward or are you still able to manage it?
Activity
melvin-bot commentedon Aug 6, 2024
Triggered auto assignment to @thienlnam (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 6, 2024
Triggered auto assignment to @zanyrenney (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.github-actions commentedon Aug 6, 2024
👋 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:
IuliiaHerets commentedon Aug 6, 2024
We think that this bug might be related to #wave-collect - Release 1
marcaaron commentedon Aug 6, 2024
Sorry, did you mean
Use Profiling?Gonna remove the blocker here. This is an internal tool and not mission critical.
10 remaining items
kirillzyusko commentedon Aug 7, 2024
It happens because "hosting" is not allowing "self-profiling":
I described it here: https://github.com/margelo/react-native-release-profiler?tab=readme-ov-file#web-support
We enabled this toggle in dev mode, but to enable it in prod (staging and prod) you'll need to add
'Document-Policy': 'js-profiling'header tohtmlresponse.I don't have permissions to deploy so I can not fix it, but if someone can shed some light on where and how the app is hosted (is it AWS S3?) then I can co-operate with that person and together we can fix that 🤞
zanyrenney commentedon Aug 12, 2024
Hey @thienlnam any progress here please? I see you added the Infra label - what's the intention for that to assign a specific person/group so that we can move this forward or are you still able to manage it?
thienlnam commentedon Aug 12, 2024
Bumped this back to a weekly since it's not high priority.
I need to double check where we want to add this header - chances are it will probably be in our salt config
thienlnam commentedon Aug 23, 2024
Nice, resolved! We only added this to staging and adhoc builds