[org.cryptomator] Can't authenticate to Google

Affected app
Name: Cryptomator
Package id: org.cryptomator

Describe the bug
Cryptomator can't authenticate to Google in order to store vaults in Google Drive.

To Reproduce
Steps to reproduce the behavior:

1. Press the + float button to create a new vault
2. Select "Create new vault"
3. Select "Google Drive" as cloud service
4. Add a new Google account or choose an existing one (if already added)
5. Type any vault name
6. Files and folders from Google drive should be shown here, but are not.
7. Press the "New folder" icon in the top right corner.
8. Type any name for the new folder and press "CREATE".
9. An "Authentication failed" error is shown. Occasionally, a crash dialog appears: "microG Services Core keeps stopping".

Expected behavior
Files and folders should be listed and accessible in the step 5.
It should be possible to create folders in the step 7.
Cryptomator should be able to read and write to Google drive.

System
Android Version: 10
Custom ROM: LineageOS with microg 17.1

microG
microG Core version: 0.2.16.204713
microG Self-Check results: All ticked

Logcat (with obfuscated data)
crash.txt

Start by reproducing the Google Drive authentication flow described in the issue on Android 10 with LineageOS and microG 0.2.16.204713, then inspect crash.txt and the reported microG Services Core failure. Done means Google Drive files and folders load, new folders can be created, and Cryptomator can read and write vaults without an authentication error or crash.