Questions

Hi all,

I’m running into a major roadblock getting Face ID/Touch ID (biometric authentication) working in my Median app, even though the plugin displays as “enabled” in the Median App Studio. I wanted to check here before escalating further with Median support.

My Setup:

Testing on Appetize.io simulator
App Public Key: pkjbyp
App Name: Clarafi-EMR
Primary URL: https://app-95142.on-aptible.com/

Problem 1: Service Config Silently Removed

When I add the faceIdTouchId config via the App Studio editor or by uploading a full appConfig.json file, the change “sticks” temporarily. But if I export the config file again, that section is silently deleted – no error, no warning.
Example config I try to add:

"faceIdTouchId": {
"active": true,
"allowedUrls": [
"https://app-95142.on-aptible.com",
"https://app-95142.on-aptible.com/*"
]
}
(Other services, including auth and barcode, save as expected.)

Problem 2: Missing Bridge Methods

Even when the UI says biometrics are enabled, the Median JS bridge is incomplete. Diagnostics show:
window.gonative_do_callback: ✅ present
window.medianInterceptConsoleLogs: ✅ present
But: window.median, window.median.auth, window.median.auth.faceId, .touchId, .status: ❌ all missing
Domain whitelisting seems to be working, since utility bridge functions are injected.

Diagnostics Page:

I’ve set up a deep diagnostics page at /dev/median-diagnostics reporting:

Bridge Status: PARTIAL_BRIDGE_NO_AUTH
Partial bridge functions present; authentication bridge totally missing
Console logging/injection works

Debug Timeline:

Error surfaced when our WebAuthn implementation failed (because window.median.auth is undefined).
Diagnostics and logging show only partial Median bridge injection.
Multiple config attempts all end with silent removal of the faceIdTouchId section, no matter how added.
Adding dummy/placeholder services also leads to silent removal.
Expected vs. Actual:

I’d expect the config to either save successfully, or return an error/warning if this feature isn’t available (maybe a plan limitation?).
Instead, I get:
❌ No error, config is just removed
❌ Biometric bridge methods never injected, even with plugin “enabled”
✅ Domain whitelist & basic plugin features work

Has anyone else seen the faceIdTouchId config get silently removed or fail to inject bridge methods?

-Is this feature only available on certain plans/add-ons?
-Any tricks to getting the config to “stick,” or might my plan be the culprit?
-If it’s not included, why no error message?
-Are there extra steps beyond adding the config to fully enable biometrics?

Would hugely appreciate advice from anyone who’s run into this—or guidance from Median staff if you see this post.

Thanks in advance for any help!