Known issues

What you may run into during the test, what is behind it, and what helps. As of 11 September 2026, phone app 0.2.30, PC app 0.2.29. Back to the tester page.

Google Play and the test

• “You are not eligible for this test” or no button on the test page. You are not confirmed in the group yet, or the browser is signed in with a different Google account than your phone. Wait for Hartwin's confirmation, then open the test page with the phone's account.
• “Your device isn't compatible.” PicHaven needs Android 10 or newer. Devices that stopped at Android 9 (for example Samsung Galaxy S8 and older) cannot take part.
• Child accounts (Family Link) cannot join Google tests. They can use the beta APK from the tester page, but they do not count as testers.
• An update does not show up in the Play Store although Hartwin announced a new version. The Play Store likes to cache the app page for a day. Usually helps: Play Store → profile picture → “Manage apps & device” → “Updates available”, then pull down to refresh. Otherwise: Settings → Apps → Google Play Store → Storage → “Clear cache”.
• The test card is missing when buying, only your real card is listed. Cancel, close the Play Store, restart the phone, try again. Google sometimes enables the test card only after a while. Never buy with real money; if it keeps failing, write to Hartwin.

Phone app

• “Thank you! PicHaven now backs up without limits” every time you open the app (version 0.2.29). Cosmetic only, the unlock is there. Fixed in 0.2.30, the update comes through Google Play.
• The purchase prompt came too early, right after re-pairing with the PC instead of after 500 new photos (versions up to 0.2.28). Fixed in 0.2.29. If you saw it: unlocking with the test card is fine and costs nothing.
• Only backs up while the app is open (Samsung, Xiaomi, Huawei, Oppo). These makers throttle background apps. When the app asks to “allow in background” or “don't optimise battery”, please agree. Otherwise set PicHaven to “Unrestricted” in the phone's battery settings.
• Nothing happens away from home. That is by design: PicHaven only backs up on your own Wi‑Fi. It has to be the same network as the PC; guest networks that isolate devices from each other do not work.
• Old photos are missing on the PC although Google Photos shows them. If Google Photos “freed up space”, the originals only live in the cloud now, not on the phone. PicHaven backs up what is on the phone. Everything you shoot from now on arrives.
• “Access problem” stayed on screen although you had just granted photo access (versions up to 0.2.28). Fixed in 0.2.29; before that, “Retry” helped.
• No dark mode. Requested and noted, coming after the store launch, on phone and PC together.

PC app (Windows)

• Windows warns about the installer (blue SmartScreen window). The test version is not signed yet. “More info”, then “Run anyway”. The Microsoft Store version is under review; that will make the warning go away.
• One admin prompt at the “Firewall” step. PicHaven registers itself once with the Windows firewall so the phone can find the PC. “Allow” is right; the question does not come back.
• After “Remove device” and re-pairing, the phone uploads everything again (PC app 0.2.29). No duplicate files are created, the PC recognises them, but it costs time and bandwidth. Fixed in the next PC version, which installs itself.
• The PC app restarts briefly. It fetches new test versions itself, never during a backup, and restarts once afterwards. The icon in the bottom right comes back on its own.
• Windows only. Mac follows later. The phone app alone is enough to count as a tester.

If something breaks

Phone: ⋮ menu → Diagnostics → Share log to [email protected]. The log contains file names and technical messages, no pictures. PC: icon in the bottom right → “Connect new device…” → “Log folder”, send the newest file. And anything that felt confusing is as welcome as a real bug.