Darkassassin07

Usually that does the trick for me too; but this morning it just would not cooperate no matter what I tried.

Seems to be playing ball again, for now.

I have a feeling this is more to do with Android/Google not wanting to give up control more than anything. If googles stuff always works, but third party stuff is mysteriously always glitchy; users are going to gravitate to google and their ever growing monopoly...

Found the best option:

There's a quick setting button you can add to the notification tray. It opens the vault and asks which item to auto fill in the app you just had open. :)

I was pointed in the direction of that menu: there's an 'autofill' button in there that will open the vault and ask you which item to use. This is so much better than android thinking about whether it should popup!

Thank you! You gave me the hint I needed.

I didn't know there was a quick setting button (the buttons in the notification tray) and have been struggling to find the accessibility options people have mentioned.

That button in the tray seems so much more reliable. Thanks again!

I had tried that; if I disable inline, I have no autofill at all.

Using SwiftKey, but I get the same results with the built in Samsung keyboard too :/

What type of auto fill do you use/works for you?

Looking into this more I've realized there are three options, but only one has ever worked for me. (talking strictly about the Bitwarden android app)

The standard 'autofill services', which is supposed to provide a popup on screen near the item to be auto filled has never worked for me. Sometimes it will flash onscreen for a fraction of a second, but always disappears before you could possibly touch or even read it.

'inline autofill' is what I have been using. It replaces the word suggestions on the keyboard with autofill options. It's what stopped working today, then seems to have come back; both unexplainably...

Finally there's the 'use accessibility' option, but the only bitwarden accessibility options I can find in android are these:

Each with 'select action' > 'bitwarden'. No other configuration, no options to choose what to do with Bitwarden, just 'bitwarden'.

When enabled the selected action enables/disables bitwarden as an autofill service to be used in the standard Android autofill services as above. I can't find anything at all in accessibility that actually triggers autofill to fill things.

I've always had all three of these autofill options enabled, but inline is the only thing that's ever actually functioned. Even still, that has been flakey, with it often not appearing in the keyboard until I move the cursor between fields several times or switch apps and come back. Today is the first time it's outright refused to show up no matter what troubleshooting I tried.

It's fixed itself and started working again, but I habe no idea why. I didn't change anything between now and when I made this post.

I tried. I couldn't get it to work again, so wanted to look at other options alongside looking for help/solutions.

But just as it decided to stop working, despite my efforts; it's suddenly started working again.

Sigh...

Vaultwarden is just a self-hosted server for Bitwardens clients. It's Bitwardens android client I've been having issues with.

That's an interesting option. It's the Bitwarden app I've been having issues with; though I'm not sure how much of that is Bitwardens fault vs Android itself.

I'll give that a look, thanks :)

That's exactly why I'm so upset about this. I don't want my passwords in my clipboard history.

Up until now, I've had some minor trouble; but usually deselecting the field you want filled and selecting it again brings up the missing autofill. That or switching apps and back.

Suddenly this morning it's completely 100% broken. I can't get ANYTHING to autofill no matter how much I try.

I stand corrected; as of today bitwarden autofill doesn't work AT ALL.

Absolutely nothing will autofill anymore.

I'm so tired of seeing this overblown reaction to ancient non-news.

Yes, there are some minor vulnerabilities in Jellyfin; but they really really aren't concerning.

Unauthenticated, a random person could potentially (with some prior knowledge of this specific issue, and some significant effort randomly generating media UUIDS to tryout) retrieve/playback some media unauthorized. THATS IT. That's the ONLY real concern. And it's one you could mitigate with a fail2ban filter if you were that worried about it.

The other 'issues' here, are the potential for your already authenticated users to attack each others settings. Who do you share your server with that you're concerned about them attacking each other???

Put this to bed and stop fussing over it. It's genuinely not worth your time or attention. Exposing Jellyfin to the net is fine.

Dev comment on the situation: (4 days ago) https://github.com/jellyfin/jellyfin/issues/5415#issuecomment-2825240290