The UpdateLead
Poshmark, Inc.'s version 10.10.04 update for its shopping app, released May 23, 2026, has introduced a critical flaw preventing users from logging in or resetting passwords, effectively locking them out of their accounts.
Rating DropUser Reception
The May 23 update to version 10.10.04 precipitated a sharp drop in user sentiment. Average App Store ratings fell from 3.18 stars to 2.47 stars after the release. This followed a period where the app had over 227,000 downloads in the preceding 30 days. The primary driver for the negative reviews is the inability for users to access their accounts.
One 1-star review for v10.10.04 states the core issue: "This app isn't working in my iphone. I asked to you send a reset to change my password since 04-22-26 and I didn't receive until now." Another review from the same period notes, "the customer service is horrible and they do not address the actual issue."
One 1-star review for v10.10.04 states the core issue: "This app isn't working in my iphone. I asked to you send a reset to change my password since 04-22-26 and I didn't receive until now." Another review from the same period notes, "the customer service is horrible and they do not address the actual issue."
The Breaking ChangeBreaking Changes
The critical authentication flaw in version 10.10.04 appears to be an unintentional software defect. While official release notes for this specific patch are unavailable, it followed a major app redesign announced on March 25, 2026, titled "Poshmark, Reimagined." This earlier overhaul introduced significant UI changes, including new portrait-style imagery and centralized seller tools.
The 10.10.04 update was likely intended as a minor patch to address issues from the redesign or to introduce smaller features, but it inadvertently broke fundamental login functionality. Poshmark has made no official public statement acknowledging the login bug or the user lockout it has caused.
The 10.10.04 update was likely intended as a minor patch to address issues from the redesign or to introduce smaller features, but it inadvertently broke fundamental login functionality. Poshmark has made no official public statement acknowledging the login bug or the user lockout it has caused.
Service and SafetyRoot Cause
The login crisis has amplified long-standing user complaints about Poshmark's customer support and on-platform safety. The Better Business Bureau has logged 1,381 complaints against Poshmark in the last 12 months[3], many citing a lack of substantive responses. This aligns with user reviews after the update that describe support as "unresponsive."
Frustration with scams and fake items, a pre-existing issue, has also intensified. A Norton security article has previously confirmed user reports of a "rapid proliferation’ of fake, scam, and bot accounts." Unable to log in, legitimate users cannot manage their listings, respond to cases, or report fraudulent activity, making these existing problems more acute.
Frustration with scams and fake items, a pre-existing issue, has also intensified. A Norton security article has previously confirmed user reports of a "rapid proliferation’ of fake, scam, and bot accounts." Unable to log in, legitimate users cannot manage their listings, respond to cases, or report fraudulent activity, making these existing problems more acute.
VerdictExpert Verdict
The failure to ship a working login system is a fundamental breakdown that directly threatens Poshmark's transaction-based business model. By locking out buyers and sellers, the bug halts all commerce for affected users. The lack of a swift hotfix or official communication suggests a potential disconnect in the company's quality assurance and incident response processes.
Poshmark will likely need to issue an emergency update to restore account access. Failure to do so quickly risks permanent user churn to competing platforms. This event underscores the necessity of rigorous testing for core functionalities before any public release.
Poshmark will likely need to issue an emergency update to restore account access. Failure to do so quickly risks permanent user churn to competing platforms. This event underscores the necessity of rigorous testing for core functionalities before any public release.