You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
device 'Model Name': iPhone 13 mini
‚Software Version' 18.2.1
"Home Assistant Companion"
in the App Configuration>About menu within the app, please include the number in brackets -->
Model Name: iPhone 13 mini
Software Version: 18.2.1
App version: 2025.1073
Home Assistant Core Version
2025.1.4
iOS App permissions for location is automatically set from ‚always’ to 'when in use'
A second iPhone 14 keeps the permission ‚always‘
Expected behavior
iOS App permissions for location keeps ‚always’
The text was updated successfully, but these errors were encountered:
Im investigating this issue for a while now, since its impossible for the app to change your permission without your authorization, this must be an iOS bug, how often does it happens to you?
With the assumption you didnt change it by accident of course
Hello, I didn’t change it by accident. The automatic change happened since installation of the HA app about fore weeks ago really often. Usually I changed to ‚always‘ and one or two days later it changed to ‚when in use‘ by itself. I opened this issue here hoping anybody can tell me, how this can happen.
I'll let you know when I have more information, for now my assumption is something on iOS side, since as I said, I couldn't even if I want code something to change the permission :/
device 'Model Name': iPhone 13 mini
‚Software Version' 18.2.1
"Home Assistant Companion"
in the App Configuration>About menu within the app, please include the number in brackets -->
Model Name: iPhone 13 mini
Software Version: 18.2.1
App version: 2025.1073
Home Assistant Core Version
2025.1.4
iOS App permissions for location is automatically set from ‚always’ to 'when in use'
A second iPhone 14 keeps the permission ‚always‘
Expected behavior
iOS App permissions for location keeps ‚always’
The text was updated successfully, but these errors were encountered: