Unfortunately, this issue is caused by changes that Google introduced in Android 12 (SDK 31+) that are not compatible with our app.

Our development team is working on a solution, and we expect a resolution by the end of March 2023.

In the meantime, as a workaround,

1. Try to perform the setup process on a different mobile device.
2. Once you have done this, you can then proceed using your Android device you wanted to use initially.