How to get rid of annoying "fill code"???

I presume you're referring to the autofill for 2FA codes sent by email or text. Short of disabling the autofill entirely, no. Only Apple can fix it. To have Apple consider your feedback, submit it here:

Feedback - macOS - Apple

I also see this in some inappropriate text entry fields, and have reported it using the above link. A short (but not that short) time after the incoming code is deleted in Mail or Messages (I have mine set to automatically delete after use), the prompt ceases.

MattBieneman wrote:

So it is just fine for Apple to add "features" that mess up everyone's software except theirs? They should have some way to turn off these kind of annoying new "features". There is no way to turn it off, and it affects many third-party applications, so it needs to be reported as a bug.

Yes, it should be reported as a bug to the developers of the 3rd party apps where you see this happening. Apple releases beta versions for a reason, it’s the developers’ responsibility to ensure compatibility.

I am having fewer problems with 2fa code now than in December, so maybe some small changes were made by Apple, just guessing, or maybe I have figured out how to use it. It was not obvious to me that after putting the cursor in the target web page's fill code area, you can just hit enter, and the fill code rectangle would go away for good, along with populating the fill code area on the site. So for a good while I keyed in the code instead of hitting enter, and then found that the rectangle had not gone away. Instead, it would for example present itself near a spreadsheet cell that I had selected, even though I had already manually entered the code into the target web page code area. The same for a word processor. I use three non-Apple apps, but give me a more useful Pages and Numbers and Safari, and I would use them. Here is an analogy: When I buy a non-digital product, I often get a user guide. Shouldn't every software update come with a user guide, or at least a list of user-relevant changes? Maybe it does, but not easy to find, I think. If you can, please post the APPLE link that tells the user to hit enter to place the code in the box, and to make the rectangle go away totally. Maybe I just do not know where to look. Or maybe the philosophy is just to let the user figure it out the hard way.

MattBieneman wrote:

Did you even read Brandnewuserid's post?

Yes.

These thousands of third party applications did not request a feature that did not even exist when they were created.

Exactly. Apple added a new feature. They release multiple rounds of beta versions of macOS so that developers can update their apps for compatibility with new features of macOS.

Even if they ignored the notice when Apple announced this new "feature", the were certainly not insane enough to request these codes in fields like "address", "zip code", "search", etc.

Evidently, they did ignore the feature in their testing of their software with beta versions of macOS.

No, they didn’t intentionally write code to request the feature after it was added, but the way their fields were coded previously obviously triggers such a request now.

There’s no need for a time machine, they just should have properly tested their software with the beta versions of macOS. Their failure to do so properly is not Apple‘s fault.

In the case of freeware, that might be challenging for developers. But that case of you getting what you paid for.

This is Apple's problem; they send these codes to fields that do not want it and did not request it.

Apple added a feature, they do that. Third parties need to keep up. If Apple adds an additional camera to the next model of iPhone, such that your case is no longer compatible even though the phone itself is the same physical size as the last model, is that Apple‘s fault? Do you blame them for adding a feature that made your case incompatible?

Well, maybe you would. But Apple provides the CAD files to case manufacturers well in advance (just as they provide beta versions to software developers), and new cases are readily available when a new model of phone launches.

That’s because the case manufacturers are responsibly keeping up with changes in the product. Obviously, developers of software that you use are failing to do so.

Apple knows about the problem. They changed their operating system to send these codes everywhere, instead of to fields that "request" them. They won't fix the problem until enough users report it as a problem.

I experienced inappropriate fill code prompts in a couple of third-party apps that I use. Turns out that, despite my earlier statement that only Apple could fix the issue, I reported it to the developers, and within a few weeks, they released updates to their software, and now the fill code prompt does not appear in their apps.

In the meantime, they could easily add a feature to "System Settings" so that users can turn this "feature" off until Apple fixes it.

If you want to keep blaming Apple for your software developers’ failure to update their apps or respond to feedback from their users, you can go right ahead. Either way, there’s nothing for Apple to fix.

Why would I need a 2FA code to post a message in a 3rd party messaging app? I wouldn't. I don't see this in macOS apps, and I suspect you're using a browser other than Safari. Not necessarily a macOS problem (given that it doesn't happen with native apps, at least for me), so would also be a good idea to provide feedback to the developer(s) of the app(s) where you see the 'inappropriate' 2FA autofill prompt.

Brandnewuserid wrote:

Ok, I confirm that Libre Office Calc spreadsheet 'wants', in your language, the 2fa code, whereas Apple Numbers does not. But is this 'loaded language'? I think if is. The implication you likely intend is that the non-Apple apps should be redesigned to reject the 2fa code.

Quite the opposite. They should not be advertising that they accept one-time codes in those fields.

Again, I don't see the logic of requiring non-Apple apps to have to add code that may create other problems, just because Apple had an idea.

The OS looks for specially coded text fields that identify as accepting One-Time codes. So, the apps you use have marked all of their text input fields as one-time code fields.

aggieash wrote:

I can confirm this is happening on Chrome (v 143.0.7499.193). It keeps offering to enter codes from Messages in random fields (e.g., username, address, search, etc.). I HATE THIS! I will report to Apple feedback, but I hope they fix this or provide the ability to control this setting sooon.

You might want to let Google know, since they are the only ones that can provide an update to Chrome to fix the problem. As stated it does not do that using the Safari browser provided by Apple.

Brandnewuserid wrote:

The unwanted fill code appears in Libre Office Writer and in Calc. I use these third party apps only because in my view Pages and Numbers are not very good. Apple needs to modify at least Pages. Safari lacks a key feature too, in my view,but that is for another original post, off topic to go farther.

But let me ask this, from my non-technical point of view:

Why is this the third party app's problem, and not Apple's problem?

Because I don't have the problem with any apps. I use a few third-party apps, but not a lot. I have never received a request to use a code unless it is the app/website/wherever that requested it.

Using 'common sense', which software may ignore, the Apple 2fa box is the 'invader', and the third party app user is the 'victim'. OK, the third party app is on the Apple hardware, but I struggle to name any other 'interference' by Apple with a third party app being used, if the app is approved. I even bought Libre Office from the Apple store. Are we that really sure that the interfering 2fa code rectangle cannot be coded by Apple to appear on Apple apps only?

The app has to advertise to the OS that you have selected a field that is appropriate for a 2FA code that was just received. Your apps are telling the OS that it wants a 2FA code.

Pages User Guide for Mac - Apple Support

Numbers User Guide for Mac - Apple Support

Keynote User Guide for Mac - Apple Support

I've never read them. I just open up the app and use it.

Autofill security codes from your iPhone in Safari on Mac - Apple Support

If you and other users would get to work and report the problem as well, then maybe Apple would do something. Hopefully informing other uses will convince them to report it also.

As far as I can tell, there is nothing for me to report. It works exactly correct. The only difference is your improperly coded third-party apps.

The problem of the fill code for 2FA popping up in many inappropriate places, repeatedly, does occur on Firefox.

You should contact Mozilla, then.

It happens to me when I have Mac Mail in the background and it happens in ANY app - check out it here in Photoshop. On Tahoe 26.3.1. Also reported.