faceid | Face Detection and Identification for Smart Toy | Computer Vision library

Do you mean?:

The answer is inside your question. You say your data was only pictures of you. That means you trained the model using photos with the same label y = 1. So it's logical that the model will always predict y = 1. If you want the model to distinguish between photos of you and photos of other people, you must train the model using both photos of you as well as photos of other people, and set y = 1 for your photos, and y = 0 for other people's photos.

Note: In your code, this if condition always returns true:

As stated by @Frightera, replacing:

model.add(Dense(classes)) by model.add(Dense(1)) should work.

Your label is an integer but your last layer output a 2d array.

I see you're calling navigator.credentials.create() in your component's componentDidMount(). macOS and iOS Safari both require that WebAuthn API calls that want to use Touch ID must be made as a result of a "user gesture":

The amount of unsolicited prompts has been surprisingly low. The situation is different with the release of Face ID and Touch ID for the web. So, Face ID and Touch ID for the web require user gestures to function. (User gestures are not required for security keys for backward compatibility.)

See Apple's introduction of their support for WebAuthn for more guidance: https://webkit.org/blog/11312/meet-face-id-and-touch-id-for-the-web/

If you update your React code to move the logic that calls navigator.credentials.create() into, say, a button click handler, you'll be able to use Face ID. It'll require you click a button to trigger WebAuthn instead of just loading the page, but that's the reality of working with WebAuthn on an Apple OS.

SOLVED The for loop should have been like this

This error always comes up for me as -1004 so I added a check to my error handling block like this:

Filed as Radar FB9039075.

A teammate (https://stackoverflow.com/users/2451589/julien-klindt, thanks for this!) received feedback from Apple (using DTS) afterwards:

The .or operator here refers to the read operation. That is, to read the item the system must be able to satisfy one or more of the specified constraints. However, things are failing in your case at the add operation. Here the presence of .biometryCurrentSet indicates that the keychain must tag the item with the current biometric set, and that can’t possibly work because no biometrics are currently configured.

So this is as designed. Apple suggest creating a feature request for the described behavior, if wanted.

In terms of workarounds, it seems reasonable to catch this error and then ask Local Authentication whether biometry is enabled. If it isn’t, you can fall back to .devicePasscode.

If it's not needed to have changes in Biometry invalidate the item, I would suggest to use .userPresence instead.

I don't think the error message really belongs to the line that causes the problem here (have you tried <<-ing the list itself before?), but

Here's an example of how you can do it without using any external application, just a text editor. But you will have to be careful to write XML code properly, or the excel file may not open correctly (make a backup copy).

1. You will create a folder named "customUI" and, inside that folder, a file named "customUI.xml"

2. You will write all your Ribbon details inside "customUI.xml". I wrote this example, covering the issues you listed: Big buttons and icons (Images list in https://bert-toolkit.com/imagemso-list.html) / Tooltip description (screentip and supertip) / Ribbon name (tab label) / Group names (group labels)