Support for FuseCapy on iOS

Before the app can do anything

The app ships without content, without an account, and without a server of its own. It needs an address to talk to. On first launch it shows one button, and what that button says depends on how you are meant to reach your server.

If you can run a command on the computer running the server

This is the shortest path, because nothing has to be typed on the phone. Run the pairing command on that computer:

• fusecapy pair, or capy pair if you use the helper

It prints a QR code. Then either tap Scan pairing code on the app's first screen, or open Settings → Scan to Pair, and point the camera at it. The address and the access token arrive together.

If you know the address

Tap Set Server address, paste the address, and tap Connect. Use the address exactly as your server reports it, including the port:

• https://your-host:9867 for a server you reach over the internet
• http://192.168.1.20:9867 for one on your own network

That screen asks only for the address. If your server needs a token and you are not pairing, enter it in Settings → Server → Connection, in the Optional Bearer token field belonging to that server.

The app cannot reach the server

• Check the address first. A wrong port is the most common cause, and it looks exactly like a server that is switched off.
• Check that the server is running. Its own logs are the authority on whether it started.
• On a home network, the first connection asks for local network permission. If it was declined, iOS stops the request before it leaves the phone; re-enable it under Settings, Privacy & Security, Local Network.
• Over the internet, use an HTTPS address. A server reached by a plain address on a public network gives no transport encryption.

Voice input

Settings offer two engines, and they are genuinely different, so it is worth knowing which one is selected.

• Apple sends audio to Apple's speech recognition.
• Online streams the audio to your own server, which passes it to whichever speech provider that server is configured with. Nothing goes to us.

Both need microphone permission, and Apple speech additionally needs speech recognition permission. If either has been refused the composer says which one, in place of a transcript — the recording never starts, which is what "it does nothing" usually turns out to be.

Where your data lives

The app keeps a local cache so the interface is usable when the network is not, but the authoritative copy of your conversations, notes, todos, mail and saved pages is on your server. Deleting the app deletes its caches; it does not touch the server. To remove something permanently, remove it on the server.

The share extension writes to your server too, and its photo-album feature saves images into your own Photos library.

Reporting a problem

The app writes diagnostic logs on the device, and Settings → About → Logs uploads them to your server. Those logs are usually what makes a report answerable — without them, "it stopped working" is all either of us has.

Email [email protected] with what you did, what you expected, and what happened instead. Reports normally get an answer within a few days.

Privacy

How the app itself handles information is described in the privacy policy for FuseCapy on iOS. What your server does with the same information is set by whoever runs that server — which, if you run it, is you.