Bugs

Reporting tab failing to generate CSV reports and send emails
What is the shop or customer experiencing? Multiple shops are experiencing failures when trying to generate reports in both the new Reporting tab and the Legacy Reporting section. Specific issues reported: New Reporting Tab: Generating a CSV report fails with error: “We could not generate this report. Try a shorter date range, or contact support if it keeps failing.” Report generation gets stuck on status: “Queued ... Keep this page open, or use Email to have it sent to you instead.” The Email delivery option is not delivering the generated reports to the users' inboxes. Legacy Reporting Tab: While specific individual reports can still be accessed, selecting the "All" button triggers a “Failed To Generate” error. Expected Behavior: CSV reports should generate cleanly without throwing errors or getting stuck in queue. The "Email" report delivery function should reliably deliver report emails to shop accounts. Clicking the "All" section under Legacy Reporting should generate and display the report data as expected. Did you replicate : Replicated on a test/support account. Attempting to generate a report resulted in the “Queued ... Keep this page open, or use Email to have it sent to you instead” state. Verified workaround: Shops can currently access specific report data using the Legacy Reporting tab (except when clicking the "All" button, which fails). Verified date range selections are correct across multiple shops and confirmed via user screenshots.
0
Facebook Live Access Token Error
What is the shop or customer experiencing: The shop owner is unable to go live on Facebook using CommentSold. After connecting or reconnecting her account in Social Setup, attempting to start a live stream fails and generates error prompts. What is the expected behavior: The shop should be able to connect its Facebook account via Social Setup and start a live stream broadcast on Facebook through CommentSold without session or token errors. What error messages are there: In-App Prompt: "It appears Facebook either Logged you out or you changed your password. Go to Social Setup to Reconnect your Account" Live Broadcast Error: Generic error prompt when attempting to go live. Backend Access Token Error: Error validating access token: The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons. Did you replicate: No What settings were checked: Social Setup Connection: Re-enabled the Facebook page in the backend, followed by a complete disconnect and reconnect of the Facebook account. Page Admin Access: Confirmed the customer is the sole admin of the Facebook Business Page. Facebook Professional Mode: Verified profile settings and turned off Professional Mode on her connected Facebook profile. Facebook Business Portfolio Assets: Checked assigned assets in Meta Business Suite and instructed the customer to select and assign the page assets. Account Password: Confirmed a password change was made on Facebook during troubleshooting. Provide examples, sku, order #, customer names, and screenshots where possible.
0
Shipping Address form broken for screen readers.
What is the shop or customer experiencing? Visually, the address form looks fine and works, but customers who use screen readers (visually impaired users) can’t fill it out easily. When they focus on the "Street Address" box, the screen reader doesn't read the name of the field. If they leave required fields blank and click "Save", the screen reader won't tell them what went wrong because the error messages aren't connected properly. What is the expected behavior? When a screen reader user lands on the "Street Address" box, it should announce "Street Address". If they leave required fields blank and hit submit, the screen reader should read out the error message (e.g., "The city field is required.") so they know what to fix. What error messages are there? The site tries to display validation errors like "The city field is required." (along with similar messages for State and Zip), but the code puts the text straight into an ARIA attribute instead of linking it to an actual message element on the page. Did you replicate? Yes. I logged into a customer account, clicked "Add Shipping Address," checked the page's code, and tried to save a blank form to test it. What settings were checked? Checked the HTML properties on the Shipping Address form elements—specifically the <label> and <input> tags, their id, for, name, autocomplete, and aria-errormessage attributes. Provide examples, sku, order #, customer names, and screenshots where possible. Timeless Threads. Shared account template, so likely every shop.
0
Load More
→