You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Bubble.io destination follows this step,
Add Bubble App Name
Add a Custom Domain Name only if the site runs on production.
Choose Environment
Provide API Private Key
Provide Datatype Name
It confuses users and they provide a Custom Domain Name which leads to data sending to the production environment. It fails for reasons like the app not being available, the app not being live, etc.
Additional context
We can bring Custom Domain Name down to Environment and only show it when the environment is in production.
The text was updated successfully, but these errors were encountered:
Greetings @chavda-bhavik , I would like to work on this issue, can you please assign it to me?
Please let me know if I understood correctly, we have to move down the custom domain name input field down a row which is below the environment input field, to prevent the failures.
Also, do you also mean to hide the custom domain name field if the environment is not in production?
Describe the bug
Bubble.io destination follows this step,
Bubble App Name
Custom Domain Name
only if the site runs on production.Environment
API Private Key
Datatype Name
It confuses users and they provide a
Custom Domain Name
which leads to data sending to the production environment. It fails for reasons like the app not being available, the app not being live, etc.Additional context
We can bring
Custom Domain Name
down toEnvironment
and only show it when the environment is in production.The text was updated successfully, but these errors were encountered: