Update 0.1.36: Sign-in and Performance Fixes

Two fixes for problems reported after Update 0.1.34, shipped the same day they were reported. Android received the sign-in fix first as 0.1.35; 0.1.36 carries both fixes to Android, iOS and Windows.

Android: sign-in refused

After updating to 0.1.34, Android players saw "This device couldn't secure the session" and could not sign in. A new build optimisation introduced in 0.1.34 removed the small component that stores your login securely on the phone, so the app refused to continue rather than keep a session it could not protect. Your account and everything on it were never affected; the fault was entirely in the app.

0.1.35 restores that component and turns the optimisation off until it can be verified on real devices before release. Update from Google Play and sign in as usual.

Freezes and crashes while moving

Players who have been with us for a while reported the game freezing as they walked, especially after a teleport, and eventually closing on its own. The cause was the map cache. Crownfront keeps recently seen map tiles on your device so revisited areas load instantly. Once that cache reached its size limit, every new tile triggered a full clean-up that examined every stored tile before removing a single old one, and it did so on the same thread that draws the game. Fresh installs never reach the limit, which is why the problem only appeared for long-time players.

0.1.36 changes the clean-up so it clears real headroom each time it runs and then stays quiet until that headroom is used, so a full pass happens rarely instead of on every tile. Nothing needs to be cleared or reinstalled; the fix applies to your existing cache the next time it fills.

How to update

• Android: update from Google Play. 0.1.35 restores sign-in; 0.1.36 follows with the map cache fix.
• iOS: 0.1.36 has been sent to Apple and will appear as an update once it is approved.
• Windows: download 0.1.36 from the website's Download page.