Dexcom Transmitter ID Detected as a Password

[databoy2k]

This is a super low priority issue, but I'm wondering if the field for the Dexcom transmitter ID is for some reason being detected as a password.

Every time I enter or change the transmitter ID, my password manager, Enpass, prompts me to save the new transmitter ID into it. See the screenshot below:

Clicking save does nothing. It's obviously not getting the right details, but something is triggering the password manager to think that the transmitter ID field is a password of some sort.

Anyone else getting this?

[databoy2k]

Could someone maybe point me to the right area of the code where transmitter IDs are entered? I could try to follow the routine and see what is tripping Enpass.

I assume other password managers (bitwarden, etc.) are not affected. Right?

[Navid200]

Why aren't we hearing this from anyone else?

If indeed something is wrong with xDrip, we will need a demonstration or a description of how to recreate the problem.

Unless you are using a phone that no one else has access to, or an app that no one else uses.

Why do you need a password manager?
Why can it not understand that the filed is not a password if you tell it once?
Have you done a search to see if others have similar issues with your password manager?

[Navid200]

This is where the transmitter ID is entered.

xDrip/app/src/main/res/xml/pref_data_source.xml

Lines 165 to 172 in 6e1f065

	<EditTextPreference
	android:defaultValue="ABCDEF"
	android:inputType="textNoSuggestions|textVisiblePassword|textCapCharacters"
	android:key="dex_txid"
	android:maxLines="1"
	android:singleLine="true"
	android:summary="@string/transmitter_id"
	android:title="@string/dexcom_transmitter_id" />

And indeed it has password as one of the input types.

[heygar]

Just so you know, it's not just Enpass. My Microsoft Authenticator pops up as well asking to save the password. As least I seem to remember it being Microsoft. It may be the Google one. Whichever one I have configured. It's not Enpass though.

[databoy2k]

Is there a reason for it to be a "textVisiblePassword" input type? Is that necessary for the software?

xDrip is the only software that I've come across as triggering this issue. It's good to see @heygar has the same issue. It's probably something that only certain password managers care about (maybe Enpass is particularly aggressive in trying to detect password fields) but the issue comes back to whether it's necessary for it to be a visible password. Honestly, I mentioned it's low priority because it's just an extra tap to make it go away. I know you're busy with WAY more important and mission-critical bugs.

I'll see if I'm able to pull a copy of the software, make the change on my end, and if it goes away. As long as there's no technical reason making that inputType critical and if it fixes it, maybe we could evaluate which if any of the fields should have that inputType?

[Navid200]

I see 20 different cases in xDrip using this format. So, the TXID is not the only one.

I suspect this is used so that the keyboard will not give you completion suggestions.

If this is really a problem and needs to be changed, the other 19 instances will need to be dealt with as well.

It doesn't hurt to compile your version and confirm that changing this will address the issue.
If it does, you will need to find an alternative way to stop the keyboard from auto completing.