eu-digital-identity-wallet / eudi-app-android-wallet-ui

EUDI Wallet Prototype
European Union Public License 1.2
51 stars 18 forks source link

mdoc verifier stuck at "Device engagement received..." #44

Closed agdolla closed 1 month ago

agdolla commented 6 months ago

Installed Android Version 2024.02.1-Demo (3) linked from README to a Samsung A13 5G with Android 14. Installed mDoc Verifier (Testing) Version 1.8 (9) also linked from README to a Samsung A40 with Android 11. When trying to verify anything the Verifier is stuck at "Device engagement received..." both with NFC and QR code. NFC and Bluetooth are enabled on both devices.

stzouvaras commented 6 months ago

Hi @agdolla,

Looking at your device's specs, I noticed that the Samsung A13 has NFC, but it is region-market locked. Are you sure your phone supports NFC and that it works as expected? Have you used it before for anything else?

Did you give all the necessary permissions to the apps? They will ask you the first time you install them.

Also, one more thing, could you please retry with NFC disabled on both devices and see if the BLE communication engages?

agdolla commented 6 months ago

Hi @stzouvaras, NFC on A13 works, I've just tried and with an application called readid I could read my id card just fine. I did not deny any permissions, currently it has only one permission: nearby devices. Screenshot_20240308_091928_Permission controller

App Verifier has no permission at all, I did not deny any permissions.

Without NFC and using QR code only and bluetooth it still does not work.

Edit: I deleted App Verifier and reinstalled it. It did not ask for any permission and after the (re)install it had no permission.

stzouvaras commented 6 months ago

Hi @agdolla,

The Verifier app should ask for permissions. Please check my screenshots. Can you please check the verifier's permission screen?

verifier_ask verifier_ask2 verifier_perms

agdolla commented 6 months ago

Installed the App Verifier on A13/Android14 and it did ask for permissions. On Android11 it did not. It might be my phone or Android11 issue so I'll install a fresh Android11 into an emulator just to find out. Not that I insist using Android11 but one of my test phones runs it.

stzouvaras commented 6 months ago

Thank you @agdolla, we will investigate further and revert.

elblasto420 commented 2 months ago

Hello, I would like to comment that, the link provided in https://install.appcenter.ms/orgs/eu-digital-identity-wallet/apps/mdoc-verifier-testing/distribution_groups/eudi%20verifier%20(testing)%20public works perfectly with the apps latest version (tried it on 2 Samsung devices with Android 14) However when using what I assume its the source code for the verifier, stored in https://github.com/openwallet-foundation-labs/identity-credential I get the same error as this issue, even using the latest code. What is more interesting is that the APK that is stored on the AppCenter has a higher version number than the latest code on that repo. Is the actual code for the AppCenter verifier somewhere else? Any help would be appreciated!

stzouvaras commented 2 months ago

Hi @elblasto420,

Our verifier application is a modified version of the repository you've mentioned. Unfortunately, the code is not publicly accessible. However, there are plans to build and release a new verifier app that will be completely open-source and available to the public, though I cannot provide an ETA at the moment.

stzouvaras commented 1 month ago

Hi @agdolla,

This issue will be closed because a new verifier application is underway, and the current one will be replaced.

You can find more information here: https://github.com/eu-digital-identity-wallet/eudi-app-android-wallet-ui/blob/main/wiki/verifier_proximity.md

agdolla commented 1 month ago

thanks @stzouvaras I will try it