Data in textInputButtonTitle and textInputPlaceholder Does Not Appear in Actionable Notification

[greg-nyc]

iOS device model, version and app version

Model Name: iPhone 11 Pro Max Software Version: 15.6 App version: 2022.3 (2022.358)

Home Assistant Core Version

2022.7.7

Describe the bug Data in textInputButtonTitle and textInputPlaceholder does not appear in notification.

To Reproduce

script:
  actionable_notifications:
    alias: AN Testing
    icon: mdi:cellphone-message
    description: Testing AN
    mode: queued
    sequence:
      - service: notify.mobile_app_phone
        data:
          message: "AN Testing"
          data:
            actions:
              - action: "REPLY"
                title: "Title Text"
                textInputButtonTitle: "Button Title Text Input"
                textInputPlaceholder: "Placeholder Text"

When running this script, the actionable notification fails to display the text in textInputButtonTitle and textInputPlaceholder

Expected behavior

Per the documentation, the data stored in these keys should appear in the notification. The text entered is, however, correctly passed back to the events bus:

...
    "data": {
        "action": "REPLY",
        "reply_text": "Testing"
...

Screenshots

Additional context

This is the first time I've attempted to use these keys, so I don't know when this bug first appeared.

[broyuken]

I just tried setting one of these up as well and neither appears. I'm on the latest HA 2022.12.7 and the latest iOS app on iOS 16.2

Also, authenticationRequired doesn't work either.

[TrumpetH4X]

Appears that this bug is still present. textInputPlaceholder and textInputButtonTitle are still not visible when configured in notifications.

[warksit]

Still ongoing. Any chance of this getting resolved? Or any pointers on where I should investigate to look at fixing it?

[WendelFelius]

@bgoncal Can you help? It’s been like this for a while now… I can’t even get it to show me the keyboard and let me input something 👎🏻

[bgoncal]

I'll try to take a look on that this week

[bgoncal]

I took a look at the code and everything seems correct, I have a hunch that this may be an issue on iOS side but I couldn't find more people complaining about it so, it will require more investigation, I will add to my backlog but can't promise it will be done soon.