Repository navigation
v0.18.1
Fix native iPhone sign-in failing with Invalid redirect URI on Home Assistant servers using a private certificate authority.
HA validates the app callback by fetching the OAuth client metadata itself. Trusting the private CA on the iPhone does not make HA trust it. New sign-ins use a small public HTTPS metadata page; authorization and token requests still go only to your selected HA server, with PKCE and state checks. Existing saved credentials retain their original client ID for refresh.
Update the iPhone app
Download RoomCall-0.18.1-unsigned.ipa, sign it with your own Apple identity and install it using the same signing/bundle identity as your current app. Then scan the QR code and sign in again. The app and widget extension report version 0.18.1, build 2.
This fix is in the native app; updating only the HA integration does not replace an installed iPhone build. RoomCall 0.18.0 on HA already provides the required backend. HA needs outbound HTTPS access to https://daredoole.github.io/RoomCall/ios-client.html for new sign-ins. Private server certificates still need to be trusted on the iPhone.
The IPA is a separate unsigned device CI artifact, not an App Store/TestFlight build. Its checksum and source run are in RoomCall-iOS-build.json; it is not covered by the integration/Python-package provenance bundle.
Validation: HA 2026.10.2 310 passed, HA 2026.2.3 309 passed + one compatibility skip, standalone 33 passed, all at 100% statement coverage. Regression tests exercise HA’s actual redirect validator, private-CA failure, public metadata, native authorization parameters and both legacy/new refresh identities. Native unit/UI/screenshot tests and device compilation are verified before publishing.
The HA integration ZIP and Python packages also carry version 0.18.1. For a manual HA update, use roomcall.zip; HACS users can use their normal update flow.