#397

First-run setup can hide unsaved loopback, pairing and conversation state

Openfoshanfmopened 6d ago

What happened

The first-run setup looked ready before all required state was actually configured.

The Local Connection screen displayed 10.7.0.1 in the loopback field even though that value was only a placeholder. After explicitly entering and saving the address, reconnecting the VPN or proxy app, and running the check again, the connection worked.

The setup screen could report that the loopback answered while RemotePairing was still unavailable. These are separate readiness states, but the UI did not make that distinction clear.

The pairing handoff was also difficult to complete. Following the written pairing instructions worked, but tapping Open Settings did not take the user directly to the exact iOS settings destination. It opened a general settings area and required manual navigation.

After changing the model provider, endpoint or key, an already open conversation continued using the previous configuration. Creating a new conversation made the new configuration take effect.

Steps to reproduce

  1. Install Poki and open the first-run setup on a physical iPhone.
  2. Open the Local Connection or Loopback setup screen.
  3. Observe the displayed 10.7.0.1 value before entering and saving a value.
  4. Run the loopback check and observe that loopback reachability and RemotePairing readiness are reported separately.
  5. Use the pairing handoff and tap Open Settings.
  6. Observe that iOS opens a general settings location instead of the exact pairing destination.
  7. Complete pairing manually by following the written path, then return to Poki.
  8. Change the selected custom model endpoint or API key.
  9. Continue using an existing conversation and observe that it can retain the previous provider configuration.
  10. Start a new conversation and observe that the new configuration is then used.

Area

Pairing or Developer Mode

App version

Poki 0.4.2 (1515) Beta

Installed with

Poki Setup 0.2.3 (1390) on macOS, free Apple account

iPhone and iOS

iPhone 13 Pro, iOS 27.0.1

Debug log

No response

Activity

2
ScottH11225d ago

Thanks for documenting each part of setup. The connection check and RemotePairing can succeed or fail independently, and the model behavior is a separate path. For the model part, could you share whether the old configuration was used on the next newly sent message, on a retry, or by a reply already in progress? Also, did you change the selected provider or edit the endpoint/key within the same provider? The provider type and timing are plenty; please leave out any key or private endpoint. That will help reproduce the same conversation path.

ScottH11225d ago

I found one concrete case in the chat code: if the custom address changes and the model name stays the same, an open conversation can keep its old connection. #428 fixes that path. The simulator regression sends two tasks from the same conversation to two local servers and checks that the second task goes to the new address. The earlier questions about retries or a key-only edit still help narrow any remaining cases. Thanks again for flagging it.