Percy common issues
Troubleshoot issues you encounter when using Percy with SDKs.
Percy is a visual testing platform that helps teams catch UI bugs. It streamlines the testing workflow by automatically capturing and comparing visual snapshots of web applications, ensuring consistent and pixel-perfect user interfaces across various environments and code changes. This page contains information on common issues, warnings, and troubleshoot method for various Percy SDKs. If you don’t find the issue you are looking for listed on this page, feel free to contact us.
Common issues
- Asset(s) never requested by asset discovery
- Assets not captured
- Assets only accessible locally
- Asset discovery timeout after 30 seconds
- Canvas elements not captured/bad state
- Videos & poster’s
- iframe content not captured (CORS)
- Unsuccessful capture of responsive DOM snapshots
- Invalid HTML
- Bad character encoding
- Chromium failed to launch browser
- Screenshots do not capture the full page
- Broken lazy loading images
- Configuring Proxy Requests
- Disallowing requests
- Disable the automatic sending of logs to Percy
- Browser upgrade issues
- Browser compatibility and maximum page dimensions
- The webpage is not loading icon assets
- Simplify Percy CLI setup with executables
- iPhone upgrade issues
- Regenerate Percy token
- Handle Safari for localhost proxy
- ShadowRoot issue in Chrome 129+
Common error messages
- Percy port already in use
- Browser launch failure
- Browser spawn failure
- Permission issue
- Network binding issue
- Build not finalized error
- Page timeout error
- Network idle timeout
- Upload snapshot failure
- No snapshots or CI pipeline error
- Incorrect project token
- Duplicate snapshot error
- Missing Percy token error
- Rate limit exceeded error
- Payload too large error
Common warnings
Troubleshooting specific SDKs
Common issues with Percy On Automate
Limitations
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!