Known Issues

The following issues are currently known and will be addressed in upcoming releases of the Wink Identity Web SDK:

Native SDK availability The current Web SDK is optimized for browser environments.
Server-side rendering limitations The SDK is designed for client-side execution. Some server-side rendering frameworks (e.g., Node.js SSR) may require additional configuration or may not be fully supported.
Enrollment conditions may impact success rate Although the enrollment flow is significantly fast, extremely poor lighting, unstable framing, or heavily obstructed faces may still cause enrollment retries.
User Profile validation is minimal At this time, the SDK does not verify the correctness or ownership of user-provided email or phone number.
Environmental noise & edge cases for voice (when used as 2FA) If Voice is enabled as a 2FA method, very noisy environments may affect success rates. To pass voice liveness, user must provide good voice without too much background noise ensuring especially the presence of 3-4 digit number being loud and clear in the speech.
Rare “Service Not Available” events Users may occasionally encounter a temporary service error due to poor network connectivity or momentary server disruptions.
iFrame and popup limitations The SDK may show inconsistencies when running inside iframes or popup windows. For best results, use redirect mode or full-page flows.
Session expiry screens In some browsers, certain yellow-state recovery screens may not auto-reset and may require the user to refresh or close the tab.
Liveness in extreme lighting conditions Very bright backlight, extremely low light, or partial facial obstruction may reduce liveness accuracy, requiring a retry.
Mobile browser engine differences Certain older or manufacturer-customized mobile browsers may handle camera permissions differently, occasionally requiring the user to grant access more than once.