-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Failing to record screenshots #334
Comments
@tripolkaandrey are you doing that? |
@sergio-sastre Thank you for your suggestion. Yes, I did enable it. |
@tripolkaandrey However, I do run it without any issues. |
No, I am using macOS. |
I am experiencing the same issue. |
Same issue... but in my another project it is working fine... Actually for the first time it worked when recording... Then it is not working.. I'm not sure why |
After few hours of debugging, I found the problem... The reason is that there are spaces in the project folder name or in the project path. Removing the spaces moved the screenshots to the project folder and fixed the error: @pedrovgs Please, fix the problem or describe it in the documentation |
My build was having minify enabled in the debug build and when i run screenshot tests for the debug build.. the screenshots were not pulled... after disabling minify, it is working find |
Preface
I am integrating screenshot testing in my Jetpack Compose application. Despite trying different library versions(5.+) and API levels(26-33), I always have some issues. I decided to pick one "combination" and, therefore, issue in the hope of getting some help—and hopefully, insight into issues with other configurations.
Dependencies
Shot => 5.14.1
Jetpack Compose => 1.3.1
Android Gradle Plugin => 7.3.1
Configuration
Sample
Device
I am launching an emulator with Pixel 6 API 30 via Android Studio.
Command
Output
Behaviour
The emulator seems to be doing the work while running the command. However, afterwards, there are no screenshots on the device and in the local
screenshots
directory.The text was updated successfully, but these errors were encountered: