Bug report from a log, secrets removed in your browser
FreePaste a stack trace, CI log or HAR file. Tokens, keys, passwords, emails and IP addresses are removed in your browser before anything is sent. You get the error, where it failed and a report you can file.
Paste a log or drop a file, then read it.
One step per line.
# Checkout button does nothing on Safari **Severity:** High **Environment:** Safari 18 on iPhone 15, iOS 18.1 ## Steps to reproduce 1. Open the cart with one item 2. Tap Checkout 3. Wait five seconds ## Expected The payment page opens. ## Actual Nothing happens and the console shows a TypeError.
### Checkout button does nothing on Safari **Severity:** High **Environment:** Safari 18 on iPhone 15, iOS 18.1 ### Steps to reproduce - [ ] Open the cart with one item - [ ] Tap Checkout - [ ] Wait five seconds ### Expected The payment page opens. ### Actual Nothing happens and the console shows a TypeError.
h2. Checkout button does nothing on Safari *Severity:* High *Environment:* Safari 18 on iPhone 15, iOS 18.1 h3. Steps to reproduce # Open the cart with one item # Tap Checkout # Wait five seconds h3. Expected The payment page opens. h3. Actual Nothing happens and the console shows a TypeError.
Written in your browser. Secrets are taken out of every field. Nothing is sent unless you keep the report.
How it works
A stack trace, CI log, browser console or HAR file. No log? Switch to Describe the bug and write what happened.
The list shows each token, password, email and IP that was taken out, and its line. Open the cleaned text to see what will be sent.
Only the cleaned text is sent. You get the error, the failing frame and a report to copy as Markdown, for GitHub or for Jira.
What it reads
It finds the error in the text you paste and the facts around it.
Up to 200 KB or 20,000 lines at a time.
| You paste | It finds |
|---|---|
| Anything with secrets in it | Tokens, keys, passwords, cookies, emails and IP addresses are removed in your browser before anything is sent. You see each one. |
| A stack trace | The error, the failing frame with its file and line, and the language. |
| A CI log | The failing step, the failed test and the runner's operating system. |
| A browser console | The error and the browser it came from. |
| A HAR file | The failed requests, with their address and status. |