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
Describe the bug
cancel button is not appearing on my dashbaord after applying the filter
On my dash board earlier cancel button is appearing ut now I am not able to see the data.
this is happening when I updated the app 9.4 version to 10.0. also not apearing on 9.4 version.
To Reproduce
Steps to reproduce the behavior:
Login with maha@calcutta_kids. on 9.4 version of app
register a individual
update the app with 10.0
sync the app
Apply the any filter
try to cancel it but there is on cancel button is present
Expected behavior
cross button should be present on filter section after applying on that
Screenshots
az_recorder_20240924_081555.mp4
ormation):**
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
Developer Checklist
Developer fixing the bug should fill this checklist.
Does the fix require extensive regression testing?
Are you mentioning the required scenarios that could be affected?
The text was updated successfully, but these errors were encountered:
Describe the bug
cancel button is not appearing on my dashbaord after applying the filter
On my dash board earlier cancel button is appearing ut now I am not able to see the data.
this is happening when I updated the app 9.4 version to 10.0. also not apearing on 9.4 version.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
cross button should be present on filter section after applying on that
Screenshots
az_recorder_20240924_081555.mp4
ormation):**
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
Developer Checklist
Developer fixing the bug should fill this checklist.
The text was updated successfully, but these errors were encountered: