Skip to main content

Tauri Example (tauri-plugin-updater)

A Tauri desktop app that uses the faynoSync JavaScript SDK for an edge-first update gate, then lets @tauri-apps/plugin-updater perform the signature-verified download and install. This maps to the tauri updater type (which requires the signature field).

Repository: github.com/ku9nov/faynoSync-tauri-example

Integration pattern​

  1. The SDK's checkForUpdates runs first as an edge-first gate. On the no-update path it answers from the CDN, so the native updater's endpoint is never hit.
  2. Only when the gate reports an update does the app call the plugin's check(), which downloads and installs with Tauri's built-in signature verification.
  3. The native updater endpoints themselves are configured edge-first in tauri.conf.json.

Creating the client with Tauri's fetch​

Tauri apps run in a WebView, so network calls go through Tauri's HTTP plugin, not the Node.js fetch. The SDK accepts a custom fetch, so the example injects @tauri-apps/plugin-http:

import { Client } from '@faynosync/sdk-js';
import { fetch as tauriFetch } from '@tauri-apps/plugin-http';

let client: Client | null = null;
function getClient(): Client {
  if (!client) {
    client = new Client({
      baseURL,
      edgeURL: edgeURL || undefined,
      fetch: tauriFetch as typeof globalThis.fetch,
    });
  }
  return client;
}

This is the main reason the SDK exposes a fetch option — it lets the same typed client run in any runtime that provides a fetch-compatible function.

The edge-first gate​

import { check } from '@tauri-apps/plugin-updater';
import { getVersion } from '@tauri-apps/api/app';

const currentVersion = await getVersion();

const resp = await getClient().checkForUpdates({
  owner,
  appName,
  version: currentVersion,
  channel,
  platform: target(),   // maps Tauri's OS name to faynoSync's platform value
  arch: archName(),
  deviceId,
});

if (!resp.updateAvailable) {
  return; // up to date — the native updater is never started
}

// Update exists -> hand off to the native, signature-verified updater
const update = await check();
if (update) {
  await update.downloadAndInstall(/* progress callback */);
}
Why gate before check()

check() polls the native updater endpoint and performs signature verification on every call. Running the SDK's edge-first checkForUpdates first means the common no-update path is answered from the CDN (and sends the optimized /telemetry/beacon), so check() — and the API request behind it — only runs when there's actually something to install. The SDK response also carries critical and changelog, which the flat Tauri updater response doesn't, so the example uses it to enrich the update UI.

target() maps Tauri's OS names (macos, windows) to the platform values faynoSync expects (darwin, windows), so the gate and the native endpoint resolve to the same artifacts. See src/updater.ts.