Connections and notifications

When you receive alerts

While Awayline is active, the herd follows your selected machine. Background refresh is scheduled by iOS and can be infrequent. A Live Activity shows the most recent snapshot and becomes stale when it cannot refresh.

On supported iPhones and iPads, Watch in the background requests a limited watch period. iOS can delay or end that request. It does not guarantee continuous monitoring. When you force-quit Awayline, open it again to resume checking. For tasks that need dependable unattended alerts, keep a separate monitoring system on the host.

Notifications belong to their original machine and session. Tapping one reconnects to that target. Deleted machines, changed connection settings, and unavailable agents require you to choose a current target from the herd.

The machine cannot be reached

Check that the address and port are correct, the machine is awake, SSH is enabled, and your device can reach its network. On a local network, check Awayline's Local Network permission in Settings. A private address usually needs the same network or a VPN when you are away.

Authentication failed

Confirm the username, private key, and passphrase. Authorize the matching public key on the target. Awayline supports OpenSSH ed25519 keys; use a dedicated key for this app. A public key file cannot sign in. Password sign-in works only if the server allows it.

SSH connected, but herdr did not

Start herdr on the machine. Check the named session or socket path in the saved machine. Clear these fields only if you want the default session. The selected socket must be available to the SSH user.

After a disconnect

Use Reconnect in the machine menu. Returning to the app also attempts recovery after a connection failure. Check the agent's current screen before resending text or an approval: a lost response does not prove the original input failed to arrive.

Sharing a useful report

Open Help → Review diagnostics, inspect the report, and share it with linyoutian.loyot@gmail.com. Include what you expected, what happened, and steps to reproduce it. Avoid sending passwords, private keys, or sensitive terminal screenshots.