ORCHARD MAINTENANCE

Bug fixes & known issues.

A plain-English log of problems we are watching and fixes that have been shipped to Fruit Merge.

Current status: Stable

No widespread gameplay-blocking issue is currently known. Items still being monitored are listed below.

BEING WATCHED

Known issues

2 open
Monitoring

Some social apps may keep an older link preview for a while

Fruit Merge now uses crop-safe social artwork, but third-party apps can cache older previews independently of the website.

What to knowUsually no action is needed. A refreshed preview appears once that service re-fetches the page metadata.
Current limitation

An unfinished game is tied to the browser where it was started

Active games are stored locally so moves stay instant and can continue through a temporary connection loss.

What to knowFinish the current run on the same browser. Completed results and account progress continue to sync normally.
PATCH NOTES

Resolved issues

7 recent fixes
Resolved Patch 07

Page could become unresponsive after a completed game

What was happening
A small number of players reported the browser showing a “page not responding” message after the result screen appeared.
What changed
Post-game input handling was tightened so stale directional input is discarded once a run has finished, preventing repeated re-entry into the game-start path.
Resolved Patch 06

Monthly leaderboard selector lost its styling

What was happening
The All Time and October 26 controls displayed without their intended segmented-control styling after the Shop page was introduced.
What changed
The missing leaderboard-period styles were restored and retained alongside the newer Shop styles.
Resolved Patch 05

Mobile leaderboard columns were misaligned

What was happening
On smaller screens, player names could disappear or scores and fruit could sit under the wrong headings.
What changed
The mobile leaderboard grid was updated to match the current four-column leaderboard structure.
Resolved Patch 04

Moves felt delayed on some connections

What was happening
Every swipe previously waited on server processing, which made rapid play feel sluggish when network or hosting latency increased.
What changed
Gameplay was moved to an instant browser-side loop. Completed games are now submitted as compact replays and verified after the run instead of blocking every move.
Resolved Patch 03

A move could trigger a spawn-configuration error

What was happening
Immediately after the new local-play system launched, some moves could display an error while attempting to spawn the next fruit.
What changed
The required spawn weighting was added to the game bootstrap data and a safe client fallback was added.
Resolved Patch 02

Assist controls could widen or shrink the game layout

What was happening
Adding Orchard Sweep made the help bar too wide in narrow centre columns and on some mobile devices.
What changed
The assist controls were rebuilt as a width-safe compact layout so the game board no longer changes size because of button labels.
Resolved Patch 01

Orchard Sweep could fail on an older database state

What was happening
The new assist briefly caused a generic service error where its supporting definition had not yet been registered.
What changed
Compatibility handling was added so the new definition can be registered safely without taking gameplay offline.
ADVERTISEMENT
SPOTTED SOMETHING ODD?

Report a bug

Tell us what happened and we’ll store the report directly in Fruit Merge. Please do not include passwords, payment details or other sensitive information.

Desktop Other Other

This page summarises user-visible issues and fixes. It intentionally does not publish sensitive security, infrastructure or anti-abuse implementation details.

YOUR LITTLE ORCHARD

Welcome