Can go part of the way there with the server-side scripts, a small prototype on this page: https://toolbox-example.bubbleapps.io/version-test/serverscript
While this hasnât been updated, my solution has been to use external endpoints (can be AWS lambda or whatever youâre comfortable with, Iâm using Python/Flask). These endpoints make the error prone calls, do error handling, and pass data back to bubble.
Though setting the endpoints up might be slightly annoying at first. I like the flexibility it provides with handling requests and dealing with things like nested fields. It also has the added benefit of letting you use SDKs and external libraries, which tends to make processes less stressful.
3 Likes
Bumping this thread - and @gevestobs same⌠Iâve been constructing Express/Node servers to handle endpoints. Agreed with your point - it does allow for flexibility, although 1) its tricky to use these combined with bubble workflows (ie., if thereâs an error, donât create this item!)⌠and 2) itâs beyond the ability of your average bubble no code user and against the âno codeâ ethos of Bubble. Overall, frustrating.
4 Likes
I am also looking for a solution to this âŚ
In this case, you could use a workflow of type âAn unhandled error occursâ. This WF will catch the error caused by a user signing in with an email address that already exists.
Although Bubble should merge accounts automatically (if we want to). This has been requested here: Email account linked with social media
Regards.
2 Likes
this feature is only available in pageâs workflows, not in API Workflows
Thatâs right. He can use it at a page level to manage authentication issues.
hey @Bubble team please prioritize this. This makes API connectors useless. It is ok for API-s to return errors in some cases and they need to be handled properly.
4 Likes
Bug, Bug, Bug alert. Seems it is a bug. When API connector call is called when page is being loaded âAn unhandled error occursâ event is not triggered. But when I call the same API connector call after a button click then âAn unhandled error occursâ event is triggered. @Bubble can you have a look on this?
1 Like
Hi @serg.sargsyan,
I suggest you to send a bug report with a specific example (with a video if possible) so
that Bubble can validate on their side.
2 Likes
Hi All,
Did anyone find a fix yet? I need to hide external API Errors from the user.
I built a calculator similar to the BMI Calculator video @bubble posted, by using the math.js API. I set up multiple inputs that calculates a result on the fly. But I also added a submit button to deliver the inputs to my database. The problem is, the math.js API reads an error when the inputs are blank. I donât allow âsubmitâ to be pressed without the inputs filled. However, the external API still sends the error based on the originally empty inputs. I donât want the user to see this error. The workflow still works and all the data is delivered and calculated correctly - but the error is sent to the user based on the initial data (which I need blank to start).
If bubble would be willing to continue with the BMI calculator video, I would suggest:
- Add a submit button to the BMI calcualtor
- Recreate the external Api error from math.js when inputs are empty
- Then show us how to hide the error message from users.
Maybe @romanmg would be interested in the next short video topic (her videos are amazing btw)?
I ran into this problem too because I need to access an URL that is sent in the header of an error response. No news here I suppose?
Oh wow! Iâve just ran into this error whilst testing a postcode looking on my site and despite the fact that I have created conditions to handle all of the errors it wont work because bubble shows their own error message which shows the user what API service that Iâm using and doesnât even display a professional message.
This is actually ridiculous! Surely there must be a solution⌠I cannot launch the app like this! People mistype postcodes all the time
Cracked it thanks to @romanmg at coachingnocodeapps⌠Iâm a member of her VIP group and she had a tutorial on bubbles ability to handle workflow errors.
I actually tried this and it didnât work but in one of her tutorials she pointed out the âAn element has an error running a workflowâ option and when I linked this up to the button is worked!
My postcode feature now works perfectly without the ugly default notifications popping up⌠I have no idea why the catch all version didnât work but Iâm very happy that itâs now working as it should be!!!
6 Likes
Good for you.
I thought it was about Backend Workflows (formerly âAPI Workflowsâ)
1 Like
This helped me. When error occurs, i just created another workflow it.
2 Likes
âAn element has an error running a workflowâ works on a page, while it is opened.
But Backend workflows are different.
2 Likes
Same issue with Backend Workflows here. If the Workflow would simply go to the next step regardless of an error like x not found, then thatâs part of the way there.
I have found a workaround for my issue in Backend workflows, where a whole workflow would stop if I was looking up a value in an API and that value was not found. Bubble would see the error and nothing else (other checks) would take place. I simply moved the one, which is likley to error to its own workflow, which I then call from the triggered workflow. Even if it errors, the original continues unhindered. Not sure if it will helpâŚ
1 Like
Dear Bubble support,
We noticed a problem/bug in the error treatment in case of an user already-signedup (with for example email, facebook or google signins), who signs up again using a different methods.
We already interacted with you about the fact that in such a case, an error is raised âErrorâs code = USED_EMAILâ. This makes the signup treatments much more complicated, but is better for security reasons you told us. Fine. However, we noticed the following problem:
-
case#1: a) If the initial signup was facebook or google, and the second attempt is by email, the WorflowErrorâmessage contains âvia Facebookâ or âvia Googleâ, which is very convenient for telling the user. GREAT. b) If this is the opposite: 1st signup=email, and 2nd signup attempt=facebook or google, then the error message is âblank[email@address]â. OKâŚ
-
case #2: If the initial signup was facebook or google, and the second attempt is another social network, for example: 1st signup=facebook, 2nd signup attempt=google, or 1stsignup=google and 2nd signup attempt=facebook, then the Error message raised in the 2nd signup attempt doesnât contain âvia Facebookâ or âvia Googleâ. Even worse, it is of the same format as in case #1b⌠which makes it impossible to disantangle the siutationâŚ
This is very ANNOYING, because we would like to simply tell the user âIt seems you already signed up with Facebook, please try to reconnect with social network for security reasonsâ -> and show them directly a Facebook login/signin button.
Could you please fix the error message in such a case (#2) please ?
Thanks a lot for your help @eve
Best regards,
Nicolas