← All release notes

FishCoin for Android — 0.1 (build 12)

What's new since build 10

versionName stays 0.1. This is a build bump, not a feature release.

Build 11 never reached anybody — Play rejected its upload — so everything below is new to you.

New since build 11

• Sending a challenge no longer double-sends. Nothing stopped two quick taps from creating two challenges while the first was still going out, and a send that waits on the network is exactly what gets tapped twice.
• Captures record at 1080p instead of 4K. This does not change measurement accuracy by a single millimetre: the measuring pipeline reduces every frame to the same working size before it looks at anything, so the extra pixels were being thrown away. It does mean smaller uploads, less of your data, and faster sending on a boat with one bar of signal.

Challenges finish now

Build 10's notes ended with "Nothing settles a finished challenge yet — scores are live throughout, but there's no final result screen." That is fixed. When a challenge's window closes the server scores it, freezes the result, and emails everyone who took part.

• A finished challenge is headed RESULT, not STANDINGS. A result labelled as a live board invites reading it as a position that might still move.
• Opening a finished challenge asks the server to settle it, rather than waiting for the fifteen-minute sweep. It cannot end a contest early — the server refuses unless the window has already closed.
• The result is frozen on purpose. Once anglers have been told who won, re-measuring a submission must not silently rewrite a finished contest.

Reviewing a result, properly

Every catch by every competitor is on the board: the picture, the measurement, where and when, the clip, and the angler's own tape figure beside the app's.

That includes the catches that did NOT count, and why. A fish the measurement pipeline would not stand behind is SHOWN and MARKED as being checked, rather than quietly missing — that is precisely the catch a losing angler will go looking for. And the board reads the same from either side; a scoreboard that differs by viewer is one nobody can argue with.

Tap a picture on the leaderboard

An angler's photo and their best catch both open full screen, with pinch to zoom.

Fixed — the leaderboard was showing the wrong people

Two separate defects, both found while reviewing the tap-to-enlarge change, and both older than it.

• Switching tabs kept the previous board's ORDER. Biggest fish, total length and fish count are three different orderings of the same anglers, and only the score text was being redrawn. The Fish-count board came out in biggest-fish order — an angler on 12 fish sitting at rank 5, beneath a rank 1 reading "1 fish". Ranks were wrong with it.
• The picture cache was keyed by RANK, which is not an identity. #3 on Biggest fish is a different angler from #3 on Total length, so switching boards drew the previous board's faces and fish against the new board's names. #1 is often the same angler on both boards, which is exactly the case that looks right while the rest are wrong. With tap-to-enlarge added, the thumbnail and the full-screen picture could be two different anglers. Keyed by picture URL now.

An angler who looks at the board here and then at fishcoin.ai/standings has to see themselves ranked identically. Until this build they might not have.

Also fixed

• One failed event load poisoned every event afterwards. The error was held on a view-model outliving the screen that read it, so after a single failure every event tapped bounced straight back to the list carrying a toast about a problem from minutes ago.
• Swipe-to-delete now asks first, and says what it cannot undo.
• A crash on save.

PvP language

Entry fees and prize pools, not stakes and pots. The rules screen argues that a challenge is a contest of skill with no house and no odds, and the next heading said "THE POT GROWS".

Underneath — email works at all now

Build 10's notes said four challenges reached nobody. That was understated. The Firebase extension that mail.ts names as its delivery mechanism had never been installed, so every message the product had ever composed — invites, lock-in notices, cancellations, event receipts — went into a collection nobody was watching. Nothing had ever reached anybody. It is installed, and verified arriving in a real inbox rather than spam.

Known limits in this build

• The settlement sweep has never run against live data. It is deployed and

green against the test suite, but no real challenge has closed yet, so the first real settlement will be the first time that path runs in production. If a challenge finishes and no result appears within about fifteen minutes, please report it rather than waiting.

• Only catches the app is confident about are counted, and that is still a

minority. Most come back as "being checked". If you land a good fish and it doesn't count, that is our measurement pipeline rather than anything you did.

• Species restrictions on a challenge aren't enforced. Nothing identifies a

species automatically, so every measured fish counts.

• SMS invites still aren't wired up. Email invites work; a challenge sent to a

phone number won't notify them.

• Tapping an angler to see their profile works on the website; the app doesn't

call that endpoint yet.

Testing behind this build

Android instrumented suite 117 passed, 0 failed iOS suite 136 passed, 0 failed, 8 skipped settlement end-to-end 24 checks against the emulator

What would help most

Unchanged, and still first: tape-measure a fish and enter the number. It is the only real reference we have, and every one makes the measurements better.

Second: finish a challenge and check the result screen against what you think should have happened — especially if you lost. That path has never run outside a test.