Setup: Pebble Time 2, macOS 26.5, pebble-tool 5.0.37, SDK 4.9.169.
iOS Pebble app version: 1.3.1.4.
Same account on CLI and app (signed in via GitHub → Firebase, one email on both).
Neither install path from the local SDK reaches the watch on the new app. Details:
CLOUD (–cloudpebble):
pebble install --cloudpebble connects to wss://cloudpebble-proxy.repebble.com/tool-v2
and prints “CloudPebble proxy authentication succeeded”, then hangs indefinitely at
“Waiting for phone to connect…”. The phone shows “connected to CloudPebble” with Dev
Connection ON and the app held in the foreground for 2+ minutes, but the tool never
receives a Connected status update from the proxy, so it never pairs.
LAN (–phone ):
The Dev Connection screen displays an IPv4, but no TCP port is ever open on the phone.
pebble install --phone <ip> returns “Connection refused” on port 9000. A full
1–65535 port scan of the phone, with the Pebble app foregrounded, shows only iOS
lockdownd (62078) — no developer server port at all. The phone is reachable at the
network layer (ping 0% loss, ARP resolves).
Only manual sideload works: download the .pbw on the phone and Share → Pebble.
Question: is the iOS developer connection (both the relay pairing and the LAN server)
expected to work in this build? Is anything required beyond toggling Dev Connection on
with a matching account on the CLI and app?