struggling with using toddle and getting auth/access tokens with xano

SWSeagull · 2024-04-15T15:59:51.755+00:00

I have been through all of the xano / toddle apps but what is not clear is when i am authenticated and when I am not. The cookie is not updating properly and if it is this difficult to use the two platforms I will go back to flutterflow.(We have built a solution with xano and flutterflow) but the ability to actually view the apis (flutterflow has a test button where you can add the access / auth token so at least you can get to the paths). The issue seems to be I am not always authenticated to view the paths (with toddle chrome extension included).Please help me as I had real hope for toddle but this initial stumbling block doesn't even let me build efficiently.Many thanks

SWSeagull
1 year ago
I have been through all of the xano / toddle apps but what is not clear is when i am authenticated and when I am not. The cookie is not updating properly and if it is this difficult to use the two platforms I will go back to flutterflow.

(We have built a solution with xano and flutterflow) but the ability to actually view the apis (flutterflow has a test button where you can add the access / auth token so at least you can get to the paths).

The issue seems to be I am not always authenticated to view the paths (with toddle chrome extension included).

Please help me as I had real hope for toddle but this initial stumbling block doesn't even let me build efficiently.

Many thanks
gazinhio
1 year ago
I use Toddle with Xano and I have the same problem with an error reported on setting the session cookie on sign-in. I can't remember if I've reported it to the Toddle fellaz before. It does save the auth token for use in the rest of the app but it does report an error in the browser console & it triggers the On Error workflow for the Set Session Cookie action rather than the On Success. If you handle it through the On Error then it will handle the auth token for you and work OK, although it seems to only authenticate for an hour, possibly 2. To be honest, I just wanted to make progress and I'd got it to work so I didn't make too big a deal of it but certainly before the app goes live I'll need it dealt with. I record it in the Feedback section. As I say, if you just wanna make progress for now, just handle it on the On Error event & hopefully the Toddle fellaz will resolve it.
SWSeagull
1 year ago
Thanks for this.

This might have something to do with it? There seems to be picking up a second (incorrectly / not set) token. One on a branch and the other in test mode?

Whether this is causing confusion I don't know but it doesn't look right.
@gazinhio
I use Toddle with Xano and I have the same problem with an error reported on setting the session cookie on sign-in. I can't remember if I've reported it to the Toddle fellaz before. It does save the auth token for use in the rest of the app but it does report an error in the browser console & it triggers the On Error workflow for the Set Session Cookie action rather than the On Success. If you handle it through the On Error then it will handle the auth token for you and work OK, although it seems to only authenticate for an hour, possibly 2. To be honest, I just wanted to make progress and I'd got it to work so I didn't make too big a deal of it but certainly before the app goes live I'll need it dealt with. I record it in the Feedback section. As I say, if you just wanna make progress for now, just handle it on the On Error event & hopefully the Toddle fellaz will resolve it.
SWSeagull
1 year ago
To check, when you say handle on error. You mean run authentication again in some way?
SWSeagull
1 year ago
Hopefully the Toddle guys will see that adding a test authentication username/password in the API config would make sense. Using cookies that do or don't work is frustrating.
gazinhio
1 year ago
No, the Set Session Cookie action runs and depending, on it's result you can set a workflow for On Success or On Error to deal with the result. It always seems to return an error event and an error is always shown in the console in the browser. Despite the error, it does seem to save the cookie correctly and you can work with it, but the On Success workflow for the Set Session Cookie never gets triggered so the steps you need to take to progress in your app needs to be put on the On Error event. Not great, but a way to make progress in the meantime.
SWSeagull
1 year ago
Ok, thank you for your help. I think I understand. I will try and have a play tomorrow.

So it is almost like success never comes back in time?
Tod
1 year ago
Great energy @SWSeagull! Your continuous contribution to the toddle Community just made you advance to Community Level 1!
@SWSeagull
Ok, thank you for your help. I think I understand. I will try and have a play tomorrow.

So it is almost like success never comes back in time?
gazinhio
1 year ago
It just errors even though it seems to do the job of setting the cookie as the auth works after that. If you check the console when you log-in, you'll see the error consistently.
SWSeagull
1 year ago
Ok, how do you handle editing other pages with other API calls if they cannot seem to access to the cookie?

I just added the success on the API call not on the submit (just used that to trigger the login call) and that seemed to work better. But I still can't set the path (on the other page) as it says "ERROR_CODE_UNAUTHORIZED"
gazinhio
1 year ago
It does set the cookie, just returns an error. So you'd call the Xano auth/login API, in the On Success event of that you'd call the Set Session Cookie but it never calls On Success on that, only On Error, although as I say it does seem to save the actual cookie despite the error. So to get the app to progress, you have to put the workflow to run next steps eg go to another URL using the On Error event of the Set Session Cookie event.
gazinhio
1 year ago
I recorded in feedback now, hopefully they'll provide a resolution shortly.
SWSeagull
1 year ago
I think my issue is slightly different - but overall the problem is the connection between the two platforms is far from perfect.
I am beginning to think it is Xano though as we did jump through some hoops with Flutterflow
and xano
gazinhio
1 year ago
I have no problem with connecting Xano and Toddle at all, this little glitch excepting, and it's lightning fast for me. I was working with Bubble and Xano previously and trust me, using Toddle is a doddle connecting to Xano compared! 😬
@SWSeagull
Ok, how do you handle editing other pages with other API calls if they cannot seem to access to the cookie?

I just added the success on the API call not on the submit (just used that to trigger the login call) and that seemed to work better. But I still can't set the path (on the other page) as it says "ERROR_CODE_UNAUTHORIZED"
gazinhio
1 year ago
On the On Success of the log-in API call, you need the Set Session Cookie action. I'll put a couple of screenshots. Also are you setting the Authorization to Bearer <access token> on the API for your subsequent API calls?
👍1
@gazinhio
On the On Success of the log-in API call, you need the Set Session Cookie action. I'll put a couple of screenshots. Also are you setting the Authorization to Bearer <access token> on the API for your subsequent API calls?
bleach
1 year ago
did u make any progress w this? im having the same issue where it only calls on error

struggling with using toddle and getting auth/access tokens with xano

SWSeagull

gazinhio

SWSeagull

SWSeagull

SWSeagull

gazinhio

SWSeagull

Tod

gazinhio

SWSeagull

gazinhio

gazinhio

SWSeagull

gazinhio

gazinhio

bleach