Skip to content

0.3.1

Choose a tag to compare

@moskovich moskovich released this 15 Sep 13:26
· 72 commits to main since this release
0c9f2cf

A truer message for a stale pairing code.

  • When a pairing code has aged out, the dialog now says the code is no longer valid, that codes expire after a few minutes, and to turn Browser Pairing on again and enter the new one. Before, the broker's answer for an expired code surfaced as "Pairing code not found on this broker", which reads like a server fault; one integrator lost half an hour to it.
  • Error codes are unchanged. pairing_code_not_found still fires for that case and pairing_code_expired remains for the broker's explicit 410. Match on codes, not on message text.
  • No API changes. A drop-in upgrade from 0.3.0.
  • Companion fix on the device side: the Feral File mobile app showed "Could not start browser pairing" in red while the FF1 was already displaying the code, whenever the phone reached the FF1 over the same wifi. That is fixed in the app and ships with its next release.

Guide: https://docs.feralfile.com/art-computer/play/