Apple has given the developer of Sparrow, a widely used Bitcoin wallet, a hard deadline: June 30, 2026, or his Apple Developer account will be shut down.

Craig Raw, the man behind the Sparrow wallet, says he was simply trying to protect iPhone users from counterfeit apps that Apple had approved. On Monday, he posted a thread on X admitting that in August 2025 he had submitted a placeholder app whose sole purpose was to warn users that the real Sparrow is desktop‑only and that any mobile version would be a fraud.

Apple rejected the submission, citing “placeholder content” that merely “demonstrated a concept.” The company then escalated the matter by threatening to deactivate the account that backs the app.

Sparrow for macOS is distributed from Raw’s own website, not the Mac App Store. During installation, an Apple Developer ID certificate signs the software, and macOS uses that certificate to confirm the software is genuine. If Apple kills the account, that action revokes the authentication certificate.

Raw warned that unless a human employee at Apple reverses the decision by the deadline, “all new installs of Sparrow Wallet will fail, and development on macOS will end.”

Apple’s own data shows that it terminated more than 193,000 developer accounts in 2025, a 32 % year‑over‑year increase. Only 499 of the 10,127 accounts that appealed were restored.

The problem began in 2023 when more than a dozen counterfeit Sparrow apps appeared in the App Store. The most recent fake app landed in April 2026. The fake software prompts the victim to type in a wallet recovery phrase, which grants hackers control of digital assets.

In August 2025, a Bitcoin holder posting as “Bitcoin Jimmy” lost 7.4 BTC – described as his life savings – after entering the seed phrase from a Coldcard Q hardware wallet into a fake Sparrow app from Apple’s store. At the time, the loss was a six‑figure sum.

Raw holds the registered U.S. trademarks for the Sparrow name and logo. On that basis, he has reported impostors to Apple since early 2024, but fake Sparrow BTC wallets kept re‑appearing.

Raw conceded that the placeholder move was clumsy. “This approach may have been misguided, but there was nothing dishonest about it,” he said. He believes the flag for deactivation is machine‑generated and expects “this is an automated misclassification that Apple would reverse on review,” but fears he “may be terminated before a human ever looks at my appeal,” with the June 30, 2026 deadline clock against him.

Many Bitcoiners tried to summon a human review at Apple on Monday. Sparrow’s own account told followers that absent a reversal, “all new installs of Sparrow will fail, and development on macOS will end.”

Podcaster Stephan Livera vouched for Raw as a “highly respected Bitcoin app developer.” Educator BTC Sessions warned that punishing the developer who flags scams creates a direct incentive for people to turn a blind eye from now on.

Apple has not publicly commented on Raw’s plea. The company’s policy states that placeholder content is not allowed and that apps must be complete before approval. The App Store Review Guidelines also require that apps be ready for distribution.

If Apple’s decision stands, users who rely on Sparrow for macOS will face a sudden loss of a trusted wallet, and the broader community will lose a tool that has been praised for its security focus. The situation also highlights the tension between app‑store enforcement and the need for developers to warn users about fraud.

At present, Raw has until June 30 to appeal. No further updates have been issued by Apple, and it remains unclear whether a human review will overturn the automated flag. The outcome will affect not only Sparrow users but also the broader ecosystem of cryptocurrency wallets that rely on Apple’s developer infrastructure.

In the meantime, users are advised to download Sparrow only from the developer’s official website and to verify that the app is signed with a valid Apple Developer ID certificate. Those who have installed the app through the Mac App Store should be aware that future updates may fail if the certificate is revoked.

The case underscores the importance of clear communication between app‑store regulators and developers, especially when the stakes involve the security of users’ digital assets.