[bvm.bvmapp] Knab app fails to load properly

Affected app
Name: Knab Bankieren
Package id: bvm.bvmapp

Describe the bug
After first run of the Knab Bankieren app you'll be presented with the Knab Bankieren splash screen, which briefly shows "Link kon niet geactiveerd worden" (Translate: Link could not be activated), and after this just seems to freeze on this screen.

Because I failed to register a device in the past using the RFID scanning method of the passport I was in possession of a device registry link, where you are able to register your device using the Knab Cardreader.
Link for this is: https://www.knab.nl/veiligheid/cardreader-registratie
On this website you click the button: "Activeer Knab App" (Translate: Activate Knab App)
This opens the Knab Bankieren app and presents you with the screen to provide Log-in credentials to the Knab financial dashboard.
Providing the credentials lets you pass to the SMS verification page.
Providing the received SMS-code lets me pass to the PIN set-up screen to choose a PIN-code to your liking to secure the app login.
After this set-up you'll immediately enter the financial dashboard for the first/possibly only successful time.
Each log-in attempt afterwards presents you with a stroboscope like PIN provider flash screen, unable to receive PIN input.
Note 1: Each screen in the device registration process briefly shows the Dutch error message "Link kon niet geactiveerd worden" (Translate: Link could not be activated)
Note 2: For each of the situations described above I provided the relevant pieces of the LogCat dumps to hopefully help me debugging this.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Aurora Store'
2. Click on 'Magnifying Glass'
3. Search for 'Knab Bankieren'
4. Follow the following steps by clicking the respective buttons: 'Download/Install/Open'
5. The following 2 situations can happen, depending on device being registered or not:
   .a) No device registration yet: Be presented with the Knab Bankieren splash screen showing "Link kon niet geactiveerd worden" (Translation: Link could not be activated)
   .b) After device registration: Be presented with a stroboscope like flashing PIN provider screen, unable to receive PIN input.

Expected behavior
The Knab app should behave exactly like it would normally do on a phone running stock android with GSF/Play Services installed on it.

1. On first launch it should normally start the device registration procedure.
2. After successful device registration it should be able to normally open the Knab Bankieren app, and present you with the PIN provider screen and be able to provide the set-up PIN-code to proceed logging in to the Knab financial dashboard.

Screenshots
Screenshot 1:
https://tweakers.net/i/n_n_ZFKKfjEhWjioy6wG83zCz_Y=/full-fit-in/4000x4000/filters:no_upscale():fill(white):strip_exif()/f/image/cuBWpM9Gc1vMfeVqu0ZQZvFZ.png?f=user_large

System
Android Version: 10
Custom ROM: LineageOS 17.1 / uG (Waydroid running on PinePhone) / Xiaomi Redmi Note 7 running LineageOS 17.1/ uG

microG
microG Core version: 0.2.22.212658
microG Self-Check results: All boxes are ticked off, in both tested environments (PinePhone / Xiaomi Redmi Note 7)

LogCat snippets

1. LogCat of first launch of Knab App showing Dutch error message "Link could not be activated" and freezes on splash screen.
   https://pastebin.com/ALAXRKY4
2. LogCat after successful device registration and first log-in right after device registration:
   https://pastebin.com/szaDDZ2v
3. LogCat of each log-in attempt after device registration, the stroboscope PIN screen.
   https://pastebin.com/DqVfdBjn

Start by reproducing the Knab Bankieren flow on Android 10 in one of the listed environments and review the three linked LogCat dumps. Compare the first-launch registration failure with the post-registration PIN-screen failure. Done means device registration succeeds and subsequent launches accept PIN input and reach the financial dashboard.