Localization: Choosing a folder outside the project in "Add Locale" throws an exception and creates no Locale assets

Steps to reproduce:

1. Create a new project
2. Install the Localization package (com.unity.localization)
3. Open Edit > Project Settings > Localization and click "Create" to make the settings asset
4. Click "Add Locale", tick two locales, and click "Add Locales"
5. In the folder dialog, navigate outside the project - for example the Desktop - and confirm
6. Check the Console and the Project window

Actual results: The folder dialog accepts the external folder with no warning. An exception is then logged to the Console, no Locale assets are created anywhere, and the locale selections made in step 4 are lost - the window has to be reopened, and the locales ticked again

Expected results: Either the folder dialog restricts selection to folders inside the project, or an explanatory message is shown, and the locale selections are preserved so the user can retry. Not a raw exception

 

Reproducible with versions: 1.5.12 (6000.5.7f1, 6000.6.0f1, 6000.7.0a6)

Tested on (OS): MacBook Pro - Tahoe 26.6.2

Notes:

• Nothing in the dialog indicates that the destination must be inside the project, and no assets are written to the chosen folder either, so the operation fails silently apart from the Console exception.
• The lost selections make the failure worse than a no-op: the user has to redo the whole selection.