Bug report: android back arrow not collapsing keyboard, removes search filter

[kaesterly]

Plan

Premium

Country

USA

Device

Google Pixel 8

Operating System

Android 15

Spotify Version

9.0.18.604

My Question or Issue

When searching within a playlist, the back arrow on the bottom of the Android screen used to collapse the keyboard, but you would still be able to scroll within the search results. Now when trying to collapse the keyboard, it removes the search filter and takes you back to the main playlist. This is frustrating when trying to search within a playlist and have half the screen covered by the keyboard.

[Ivelina]

Hello there @kaesterly,

Thanks for posting in the Community and welcome!

Did you notice if this started happening after something specific? Are you using the default keyboard of the phone or a custom one? If you're using a custom one then it's possible that it's causing this performance issue and it'd be great if you could send us a screenshot or two so we can check how things look like from your end.

You can attach the images to your next response via the Insert Image option in the post editor.

Additionally, in case you've not performed any troubleshooting so far, you can give Spotify a clean reinstall with the steps here as this often helps resolve different issues. The steps also include clearing the cache which can cause trouble when it's corrupted.

Keep us posted 🙂

[kaesterly]

Hello,

I am not using a custom keyboard. Keyboard is the factory installed
keyboard for the Google Pixel ('Gboard'). I followed the steps for both a
regular app reinstall and a clean reinstall and the issue still persists.

[Maria]

Hey @kaesterly,

Thanks for following up and for the additional info!

It is possible that this could be related to the setup or perhaps specific device settings. And in this case we suggest reaching out to the device manufacturer for further help. It's also worth having a look through your phone's settings, just to check if you notice any features or enhancements that are switched on, which might be causing the behavior you're describing.

We're just a post away if you need anything else! Cheers.