You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Credential Provider displaying “Bluetooth not started correctly”

APIIDA Mobile Authentication uses the Bluetooth interfaces provided by Windows. This dependency is declared and is taken into account by Windows when starting up the different services. Occassionally this scheduling fails and starts Mobile Authentication before starting the Bluetooth interfaces. If this happens APIIDA Mobile Authentication is not capable of communicating correctly and is displaying this error message on the logon UI. Please click “Reconnect” right below the message. This forces the restart of the Bluetooth interfaces allowing APIIDA Mobile Authentication to use it correctly. Please note that during this process any other Bluetooth accessories like headsets are re-connected as well.

App and Windows client are unable to connect to each other

When connecting the app tries to establish the Bluetooth connection and fails, displaying an error screen. The credential provider on Windows still shows “Ready to connect”. In this case please click the “reconnect” link right under the message on your Windows logon screen. This will restart the Bluetooth stack in Windows. If this does not fix your problem, try closing the app on your phone. On Android you might have to forcefully close the app. For guidance on how to do this consult the manual of your phone.

  • No labels