I started using the Real Estate template for my app, and I’m so close to publishing it on the app store! Super exciting stuff… except there’s one problem I can’t figure out. Whenever a user signs up on the app, the app still sends out the “welcome to Giran” email to their email. I have searched through all of the actions attached to the submit buttons and forms, but cannot figure out where this is coming from. Does anyone know how to fix this?
Checked that as well - unfortunately, no luck. I wonder if there’s a way that it’s stuck on the backend? I’m not sure how the API could still be connected though when its not showing as a custom action… very confusing, for sure.
Ok, I guess you’ve faced the bug which is quite rare.
My hypothesis here is that you have a button/element in your app, which was copied from another app from different account. And in that 1st app this button/element had a Custom Action which was attached to it.
Upon copying to a new app to a new account, the Custom Action has disappeared. Though it still kept attached to a button/element. And it is still executed when button is pressed.
I had the same issue (email sending) when I copied the button from the account in one app to another… no custom actions, nothing should happen, but email appears :))
Workaround is simple - try to understand which element triggers the action, and delete it, and create again
It’d be interesting to know if my hypothesis is correct
I checked the blank sign up screen, but the only action there is an action to link to the home screen. I think I’m going to try to recreate these screens from scratch and see if it still sends the email. From what @Victor suggested it seems like that might be a good option since I don’t really know which individual component is causing the issue.
As an advice - when you debug things like this, try to change components one-by-one and run a test after each change. This will help you to understand which exact part was causing the problems.
Based on what @Shinnawy wrote I think that if you recreate the blank screen (delete the screen and add new one), the problem should disappear. But I might be wrong
Ahh, yeah I guess that would be best practice for debugging. I’ll keep that in mind - I appreciate the advice! I’ll let you know what the result is after I test it out.