I am puzzled about what is the right way to arrange testing collaboration of the Workspace add-on, as there seem to be two different places to share the test access (none of which works for me quite yet): the access sharing from the Apps Script UI, and the Test users listing under the attached GCP project.
Any hints would be appreciated! :)
The things that confuse to me:
The documentation seems to say I would need to give editor access to the script project to a tester. However, when I share the app script project edit access to somebody, then they can open the app script project, but when they click on the Deploy > Test deployments, they get the error message "Something went wrong. Please reload the page to try again."
What is the meaning of adding "Test users" to the OAuth consent screen of the attached GCP project? What is the effect of adding or not adding somebody there while I would have to share the script project from the Apps Script UI with editor access anyways (having user listed in the "Test users" list didn't solve the "Something went wrong" error message)? If those "Test users" should be able to add the not yet published add-on to their workspace, then how exactly? The bubble-tooltip when you hover over the ?-mark at "Extenal" type says: "Your app will only be available to users you add to the list of test users." Then how those test users can add that app? The app is not yet published -- it is not yet searchable from Marketplace -- where is the UI feature that would allow test users listed here to add the add-on that is in External/Testing state?