Silent Maintenance Break
LeadBehind the generic changelog, the build modified session-token refresh routines and network verification protocols. These adjustments created severe login bottlenecks across mobile devices, turning a routine patch into a disruptive service interruption.
Changelog vs Reality
Release SummaryTechnical inspections indicate that the binary updated client build targets and multi-factor verification handshakes. Instead of smoothing background processes, the modified code triggered aggressive anti-bot heuristics that misidentified standard mobile logins as suspicious behavior.
Verification Loop Collapse
Breaking ChangesAs one 1-star reviewer on v352.1 stated, "Doesn’t let you create an account, constantly does circles when trying to ‘prove your a human’ just starts over, also doesn’t send text messages for approval." Another 1-star user noted the app "keeps on making me verify my identity, signs me out."
A thread on r/discordapp describes users trapped in identical hCaptcha loops where finishing challenges routes straight back to sign-in screens.
Sentiment Inversion
User ReceptionBy contrast, version 352.1 generated severe backlash over baseline instability and sluggishness, with a 1-star reviewer describing the client as "slow laggy garbage". The inability to maintain an authenticated state prevented communication and server browsing for established accounts.
Audience Fallout
MonetizationInvoluntary sign-outs lock subscribers out of premium Nitro perks and active server chats, while completely stopping new registrations.[4] When baseline authentication fails at this volume, onboarding drops sharply and recurring mobile revenues face immediate friction.
Recovery Outlook
Expert VerdictThese figures compare the 104 US App Store reviews tagged with v352.0 against the 172 tagged with v352.1, measured on 2026-11-15. While technical remediation may happen quickly, lingering negative review cohorts suggest sentiment metrics will take weeks to normalize.