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
Model Name: iPhone 15 Pro
Software Version: 17.4.1
App version: 2024.624
Home Assistant Core Version
2024.4.4
Describe the bug
The iOS Companion App appears to be modifying the Name component of iOS action by adding trailing whitespace to actionName values sent to HA, which prevents automatons triggered by an actionName from running. Below is an example of an action received where there is trailing whitespace in actionName. This action was working correctly yesterday, as I had troubleshot the issue already once and manually repaired it on all devices.
The issue is fixable if you go into the Companion App, delete the name fully and add new text such as a single letter, save it, and then go back again to modify the name a second time. The whitespace should now be accessible in a new location, normally as a leading whitespace instead of a trailing one. After following this procedure the action works again, though quotes are also no longer present in the name:
To Reproduce
The issue can be forced to be reproduced quite easily, but the forced reproduction doesn't explain all scenarios of how it can arise. Forced Reproduction Methods
Create an iOS Action in the Companion App and provide it a name. Add a space after the name. The space will be entered as a valid character but will not appear visually in the name field and you will not be able to remove it without following the procedure listed above.
Create an iOS Action in the Companion App and provide it a name, but use AutoComplete for the final word. The same situation will arise as Forced Method add more linked files #1.
Otherwise, you can try what has happened to me:
Create an automation keyed off an actionName and not an actionID, create an iOS action that has the same name, and wait a few days. The action will stop triggering and a trailing space will be present in the actionName being sent to HA.
Expected behavior
No trailing spaces sent in actionName
Trailing spaces are not automatically inserted into the Name field for Actions in the iOS Companion App
Trailing whitespace characters are visible and editable inside of the Companion App.
Screenshots
This is how it appears inside of the companion app:
Note that there does not appear to be any whitespace in the highlighted section.
This is what it looks like after following the procedure I listed above, but note it looks exactly the same. However, the data being sent now omits a trailing whitespace.
Additional context
This has occurred on at least two devices. Initially discovered the issue when actions failed to trigger on my partners device. Troubleshooting lead me to find it on mine as well and have had to correct it a few different times now.
actionName is important to me because it allows me to create a single automation with a single trigger that can work across devices. While I understand I can also use actionID, it is difficult to pull them off devices and requires more long term maintenance.
The text was updated successfully, but these errors were encountered:
iOS device model, version and app version
Model Name: iPhone 15 Pro
Software Version: 17.4.1
App version: 2024.624
Home Assistant Core Version
2024.4.4
Describe the bug
The iOS Companion App appears to be modifying the Name component of iOS action by adding trailing whitespace to
actionName
values sent to HA, which prevents automatons triggered by anactionName
from running. Below is an example of an action received where there is trailing whitespace in actionName. This action was working correctly yesterday, as I had troubleshot the issue already once and manually repaired it on all devices.The issue is fixable if you go into the Companion App, delete the name fully and add new text such as a single letter, save it, and then go back again to modify the name a second time. The whitespace should now be accessible in a new location, normally as a leading whitespace instead of a trailing one. After following this procedure the action works again, though quotes are also no longer present in the name:
To Reproduce
The issue can be forced to be reproduced quite easily, but the forced reproduction doesn't explain all scenarios of how it can arise.
Forced Reproduction Methods
Otherwise, you can try what has happened to me:
Create an automation keyed off an
actionName
and not anactionID
, create an iOS action that has the same name, and wait a few days. The action will stop triggering and a trailing space will be present in the actionName being sent to HA.Expected behavior
actionName
Screenshots
This is how it appears inside of the companion app:
![IMG_0226](https://private-user-images.githubusercontent.com/1262368/326946582-cbe1960a-6744-40a8-af5b-14929a43bcdf.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwNTc2MDMsIm5iZiI6MTcyNDA1NzMwMywicGF0aCI6Ii8xMjYyMzY4LzMyNjk0NjU4Mi1jYmUxOTYwYS02NzQ0LTQwYTgtYWY1Yi0xNDkyOWE0M2JjZGYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgxOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MTlUMDg0ODIzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MmQwYmQ4ZjdkYmQ2MjM0YjNkZmFiZjIzZTQ1NmM1ZjkyMTA3NDc5MmY3ZmFmNTNiMDAxNTIwNzQ1NGVmNjM2MyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.qZ-FOB1W-jQsZrjlgYDKr7Tsx1OSouNJEwAwpYOQG44)
Note that there does not appear to be any whitespace in the highlighted section.
This is what it looks like after following the procedure I listed above, but note it looks exactly the same. However, the data being sent now omits a trailing whitespace.
![IMG_0228](https://private-user-images.githubusercontent.com/1262368/326950914-a433596d-494e-40eb-a4ad-cf7f2e1f4ca0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwNTc2MDMsIm5iZiI6MTcyNDA1NzMwMywicGF0aCI6Ii8xMjYyMzY4LzMyNjk1MDkxNC1hNDMzNTk2ZC00OTRlLTQwZWItYTRhZC1jZjdmMmUxZjRjYTAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgxOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MTlUMDg0ODIzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDBlN2EzY2MwNjAyMGI5MTU3Nzc1NGY2MmI2ZWRjYjBlYjJlNzY0M2JjOWVmMzJjMDc2NGFmMmUxNGQwMWNhMiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.ap0lqHc7MlH6Ht81RrabvLmyt9NwluLrNwkkNkhaWwU)
Additional context
This has occurred on at least two devices. Initially discovered the issue when actions failed to trigger on my partners device. Troubleshooting lead me to find it on mine as well and have had to correct it a few different times now.
actionName
is important to me because it allows me to create a single automation with a single trigger that can work across devices. While I understand I can also useactionID
, it is difficult to pull them off devices and requires more long term maintenance.The text was updated successfully, but these errors were encountered: