The codelab doesn't mention anything about setting up the consent screen.

[AviusX]

While it is a fairly straightforward process, the codelab doesn't talk about setting up the consent screen and scopes through it or the fact that you need to go through the verification process if the scopes mentioned in the consent screen fall into the "Sensitive" or "Restricted" categories (without which the "unverified app" warning will be displayed and the user cap will apply).

The scope of the activity falls into the "Restricted" category.

Also, the scope should be https://www.googleapis.com/auth/drive.metadata.readonly instead of drive.readonly.metadata as mentioned in the codelab's sample code line 7:

SCOPES = 'https://www.googleapis.com/auth/drive.readonly.metadata'

This is correct in the drive_list.py in the repository but not in the actual codelab.

[wescpy]

• Consent screen info added (to Module 7 in the codelab) in May 2021
• Will close after the scope string has been updated