Webinterface Notification panel report "Bad Attachment" when none as been chosed

[federicofortini]

:beetle: Describe the bug In version 0.9.8 the "notification" panel used to test configuration report an error: "Failed to send the notification(s).Bad attachment" even if did not chose anything at all. Notification invoked from CURL works fine.

:bulb: Screenshots and Logs 2024-01-29T17:06:08.741289391Z 2024-01-29 11:06:08,740 [WARNING] django: NOTIFY - 172.18.0.15 - Bad attachment specified 2024-01-29T17:06:08.742333386Z 2024-01-29 11:06:08,741 [WARNING] django.request: Bad Request: /notify/apprise 2024-01-29T17:06:08.743187507Z [pid: 147|app: 0|req: 52/72] 172.18.0.15 () {94 vars in 3559 bytes} [Mon Jan 29 11:06:08 2024] POST /notify/apprise => generated 14 bytes in 6 msecs (HTTP/1.1 400) 5 headers in 290 bytes (1 switches on core 0)

Here the screenshot from UI:

:computer: Your System Details: Docker container by Linuxserver: https://github.com/linuxserver/docker-apprise-api/releases/tag/v0.9.8-ls113

:crystal_ball: Additional context Create a telegram configuration, mine is: me=tgram://bot:key/chatid/?silent=yes go to "notification" tab and subit a test notification

[caronc]

That's really interesting, i can't reproduce that here. What browser (and version) are you using?

[federicofortini]

Goodmorning, I tested:

• BRAVE v1.62.153 - Windows 10
• Chrome 120.0.6099.231 - Android 14
• Chrome 106.0.5249.119 - Windows 10
• Firefox 120.0 - Windows 10

Let me know if i can do some additional test.

Federico

[federicofortini]

I tried also with caronc/apprise-api docker image, nothing changed.

Federico

[caronc]

I think i fixed this :rocket:

[federicofortini]

With latest version it works.

Thanks, Federico