unsend-dev
🐞 - Application error: a client-side exception has occurred
What happened?
My fresh unsend instance app crashes when clicking the "Add Domain" button and shows the common client-side exception white screen with the message: "Application error: a client-side exception has occurred"
Browser console displays the following error:
Error: A <Select.Item /> must have a value prop that is not an empty string. This is because the Select value can be set to an empty string to clear the selection and show the placeholder.
Replication Steps
- Deploy a fresh unsend instance
- Navigate to /domains
- Click the "Add Domain" button
Self hosted or Cloud?
Self hosted
What browsers are you seeing the problem on?
Chrome (or chrome based like Brave, Arc, etc)
hello it should let you to go to domains,
did you finish this process btw? https://docs.unsend.dev/get-started/self-hosting#step-3-setting-up-a-region
hello it should let you to go to domains,
did you finish this process btw? https://docs.unsend.dev/get-started/self-hosting#step-3-setting-up-a-region
Thanks for taking a look at it!
Yes, I did follow the setup process as specified in the docs. Now here's the thing: the issue isn't with navigating to the "Domains"page but rather when clicking the "Add Domain" button. right there the app just crashes on click.
@KMKoushik recording
Error message in browser
3786-5c16ce142dbf441d.js:1 Error: A <Select.Item /> must have a value prop that is not an empty string. This is because the Select value can be set to an empty string to clear the selection and show the placeholder.
I was using Coolify 1-click implementation, my suspicion is that in the first configuration in the Add a new SES configuration Dialog, I left Region empty (I thought it would be inferred to the value us-east-1) and this will cause problems with the shadcn <Select> because the value cannot be undefined.
It's strange because I tried to do this again in a new instance of unsend and I couldn't replicate the error, it seems like there is a validation in the form and an error is displayed, but I'm sure that in some situation it is possible to create a SES configuration without the Region value and this will generate problems in the application as we are seeing here.
I tried quickly but I couldn't replicate it in a local environment.
For friends who still have this problem (@amkayondo and @rokitgg), please send a print of the /admin url of your instance, I bet that in the SES Configurations table there will be at least one Region entry with an empty value.
@KMKoushik The problem.
I just inserted a new SES configuration and two SES configurations were created, the first one is the one I wanted to create, the second one is very strange and has no Region defined.
Since it has an empty Region, it will give an error in Select
