Adjust LocationForSecureConnection wording#6509
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the onboarding/settings “LocationForSecureConnection” messaging so the screen can show different explanatory text depending on whether the server configuration includes any plain HTTP URLs.
Changes:
- Split the secure-connection explanatory string into a generic version and an HTTP-specific version.
- Add
hasPlainTextUrlwiring fromLocationForSecureConnectionViewModelinto the screen to choose the appropriate message. - Extend unit and screenshot coverage to validate the HTTP-specific variant.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| common/src/main/res/values/strings.xml | Adds a new HTTP-specific string and adjusts the generic content string. |
| app/src/main/kotlin/io/homeassistant/companion/android/onboarding/locationforsecureconnection/LocationForSecureConnectionViewModel.kt | Exposes hasPlainTextUrl as a new flow for the UI to branch on. |
| app/src/main/kotlin/io/homeassistant/companion/android/onboarding/locationforsecureconnection/LocationForSecureConnectionScreen.kt | Plumbs hasPlainTextUrl into the UI and selects the appropriate string resource. |
| app/src/test/kotlin/io/homeassistant/companion/android/onboarding/locationforsecureconnection/LocationForSecureConnectionScreenTest.kt | Adds a test case and updates expectations to account for the conditional text. |
| app/src/screenshotTest/kotlin/io/homeassistant/companion/android/onboarding/locationforsecureconnection/LocationForSecureConnectionScreenshotTest.kt | Adds a preview/screenshot scenario for the HTTP variant. |
...anion/android/onboarding/locationforsecureconnection/LocationForSecureConnectionViewModel.kt
Outdated
Show resolved
Hide resolved
...nion/android/onboarding/locationforsecureconnection/LocationForSecureConnectionScreenTest.kt
Show resolved
Hide resolved
Test Results 94 files 94 suites 10m 53s ⏱️ Results for commit 56d389c. ♻️ This comment has been updated with latest results. |
| <string name="location_sharing_no_share">Do not share my location</string> | ||
| <string name="location_secure_connection_title">Let us help secure your remote connection</string> | ||
| <string name="location_secure_connection_content">It appears that your connection is not encrypted (using HTTP). If the app knows when you\'re away from home, it can choose a more secure way to connect to your Home Assistant system if available. This requires location services to be enabled.</string> | ||
| <string name="location_secure_connection_content_http">It appears that your connection is not encrypted (currently using HTTP).</string> |
There was a problem hiding this comment.
The check from a technical view is 'does the server have any plain text url'. This text suggests you are currently using a plain text url.
There was a problem hiding this comment.
What about currently using HTTP in your configuration?
jpelgrom
left a comment
There was a problem hiding this comment.
Let's go with this for now and see if it helps reduce confusion
Summary
This PR adjust the wording of the LocationForSecureConnection screen to match the current configuration and not a generic one that was missleading for some users.
Checklist