When my backend returns an error 500, my entire fr...
# support-questions-legacyl
lfhenriquez
11/21/2022, 2:34 PMWhen my backend returns an error 500, my entire frontend goes down because Supertoken ask me to wrap the entire app in SuperTokensWrapper which doesn't see to handle errors properly... How can I avoid that?
r
rp_st
11/21/2022, 2:34 PMhey @lfhenriquez this happens cause you need to add an error boundary in your app
l
lfhenriquez
11/21/2022, 2:35 PMI have one!
r
rp_st
11/21/2022, 2:35 PMoutside the supertokenswrapper?
rp_st
11/21/2022, 2:35 PMperhaps @porcellus can help here
l
lfhenriquez
11/21/2022, 2:36 PMI could add one outside supertokenswrapper, but even if it catches the error, my entire app which is inside the wrapper will be down...
p
porcellus
11/21/2022, 2:36 PMyep, it should be outside that as sometimes that'll get errors.
porcellus
11/21/2022, 2:36 PMhi 🙂
porcellus
11/21/2022, 2:37 PMbut yeah, a 500 response to the refresh api could cause something like this.
l
lfhenriquez
11/21/2022, 2:37 PMSo what should I do ?
lfhenriquez
11/21/2022, 2:38 PM(by the way thanks for your quick answer!)
lfhenriquez
11/21/2022, 2:39 PMI know I should do anything to prevent an error 500 on this endpoint but unfortunately due to some constraint it does happen during a few seconds during my deploy...
p
porcellus
11/21/2022, 2:39 PMI'd say add a handler outside the wrapper for this. I'm not sure if there is a better way.
porcellus
11/21/2022, 2:41 PMBtw, does this only happen if your refresh endpoint throws?
l
lfhenriquez
11/21/2022, 2:42 PMI'd say add a handler outside the wrapper for this. I'm not sure if there is a better way. ----> I've tried to do it but doesn't work 😢
lfhenriquez
11/21/2022, 2:42 PMBtw, does this only happen if your refresh endpoint throws? ---> I'm sorry, what do you mean?
p
porcellus
11/21/2022, 2:43 PMDo you only get this error screen if the refresh endpoint returns a 500 error?
porcellus
11/21/2022, 2:44 PMor does this happen any time you get a 500?
porcellus
11/21/2022, 2:56 PMalso, does the error boundary work if you don't wrap it with
SuperTokensWrapperporcellus
11/21/2022, 3:09 PMI meant if you don't have the SuperTokensWrapper inside it.
l
lfhenriquez
11/21/2022, 4:14 PMTo my knowledge it only happens if the refresh token return an error 500 (not the other endpoints)
lfhenriquez
11/21/2022, 4:17 PMIt does seem to "dodge" my error boundary...
lfhenriquez
11/21/2022, 4:18 PM(by the way I found an easy way to reproduce this error by blocking the request in chrome)
p
porcellus
11/21/2022, 4:31 PMhmm. that's strange. I'll check it out in a bit and get back to you.
porcellus
11/21/2022, 4:34 PMbtw, do you happen to have a repo where I could test this?
l
lfhenriquez
11/21/2022, 5:39 PMUnfortunately it is on my company app so I can't share it 😢
p
porcellus
11/22/2022, 7:46 AMThis doesn't seem to be happening in our example. Even without an error boundary if I block the request I only get redirected to auth.
l
lfhenriquez
11/22/2022, 9:41 AMOk... That's weird because the request is made by SuperTokens and I don't modify it...
lfhenriquez
11/22/2022, 9:41 AMHow could I dig into it?
p
porcellus
11/22/2022, 10:32 AMWell, it may be just that I missed something during the reproduction
porcellus
11/22/2022, 10:33 AMOne way could be to try and check if it happens in our example
r
rp_st
11/22/2022, 10:33 AMcan we get on a call @lfhenriquez to help fix this?
l
lfhenriquez
11/22/2022, 5:19 PMYes @rp_st it would be awesome! Here is my calendly to find a time slot: https://calendly.com/leonard-capsule/
r
rp_st
11/22/2022, 5:35 PMawesome! have scheduled it. thanks