-
Notifications
You must be signed in to change notification settings - Fork 180
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
[BUG] Screenshots path is empty. Sceenshots won't work #264
Comments
bump |
This is fixed in catcher_2 |
I will give it a try thanks |
I try using catcher 2 but it not working |
Edit: Also your issue is different. This issue (#264) is about a crash related to the screenshot manager (which is fixed in |
i don't think the configuration is wrong because it was working 2. |
@AnhTH260101 Please open an issue using the proper template and provide code etc.: https://github.com/ThexXTURBOXx/catcher_2/issues/new?assignees=ThexXTURBOXx&labels=bug&projects=&template=bug_report.yaml&title=%5BBug%5D%3A+%3CChoose+an+appropriate+title%3E |
Describe the bug
I got a warning and the stack trace from Catcher that screenshot path is empty after initialize catcher in SilentReportMode and ConsoleHandler when my app is starting.
I don't want to have any screenshot saved is this possible to disable screenshots ?
it's not the same comportment in PageReportMode and ConsoleHandler, no page report and any stacktrace linked to the screenshot path is empty
Is this intended ?
To Reproduce
Screenshots
Flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.0, on Linux Mint 21.2 6.2.0-36-generic, locale fr_FR.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2022.3)
[✓] Connected device (3 available)
[✓] Network resources
Catcher version
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: