Cryptic Console error is thrown instead of a user-facing explanation when the Localization package's Google Sheets Extension actions fail due to unauthenticated OAuth credentials

How to reproduce:

1. Create a new project with the “Universal 3D” template
2. Install the Localization package (Open Window > Package Management > Package Manager, then in this window select “Unity Registry” from under “Sources” and type in “Localization” in the Search field, then select “Localization” and click “Install”)
3. In the Menu Bar, click Assets > Create > Localization > Google Sheets Service
4. In the Inspector, for the Authentication property dropdown, select the “O Auth” option
5. Enter “randomtext123” for Client Id and Client Secret
6. In the Menu Bar, click Window > Asset Management > Localization Tables
7. Click the “Create” button in the window that opens
8. Hit “Save” in the File Dialog that opens
9. Press “+ New Table Collection”
10. Press “Locale Generator”
11. Enable the checkbox for “Arabic”
12. Press “Add Locales”
13. Enter “arabic” for the filename in the File Dialog and hit “Save”
14. Press “Create”
15. Enter “stringtable” for the filename in the File Dialog and hit “Save”
16. In the Project window go to Assets > stringtable
17. Select “New Table” in this Project window
18. In the Inspector, under “Extensions”, click the plus icon and press on “Google Sheets Extension”
19. In the Project window go to the Assets folder and from there drag the “Google Sheets Service” Asset into the “Sheets Service Provider” property field in the Inspector
20. In the Inspector, press “Create New Spreadsheet”
21. Observe the Console

Actual result: Error appears in Console: ”Create Spreadsheet: Failed”, “RunSynchronously may not be called on a task not bound to a delegate, such as the task returned from an asynchronous method”

Expected result: A proper explanation on why the spreadsheet doesn’t get created

Reproducible with: 1.5.1 (6000.0.0f1), 1.5.11 (6000.5.0b12, 6000.6.0a7)

Reproducible on: Ubuntu 24.04.4 LTS
Not reproducible on: No other environments tested

Notes:

• CQA could not reproduce the issue in the same way as the user, but the user were getting the same error even after successfully completing the authorization through the Google Sheets Service asset