Thank you for your question and sorry for replying a bit late.
My Backendless trial has expired and the environment has been deleted. From what I remember, I used the graphical function creator (that “puzzle”-like interface). I have wrapped the 1.) signup function AND 2.) login function (using the signup credentials) into a new, outer function, called signin (SIGN up and log IN ). Within that outer function, I retrieved the User ID and Token, and returned these by the outer function.
The registration function in a pseudolanguage (and not bullet-proof):
Regarding the backend comparison. I liked most of them. My most favorite is without doubts Supabase. They are using exclusively very stable open source components in their backend as a service. Price/Performance is absolutely fantastic.
Xano though, is maybe my 2nd favorite. The problem is, that they are not GDPR compliant (yet). At least they weren’t while I was trying Xano. They said they had some other strong security certifications, but explicitly stated that GDPR is something they need to work on.
I am also facing the FATAL ISSUE of Problem 1 that you mentioned. I think this is still not resolved.
I contacted Adalo Support about this, but got the following misguided response:
As far as how things are configured, this is still in beta and because API set up can vary, I don’t know the exact requirements. It seems likely there is an issue with the way you have set up the ID and the lack of authorization but I can’t be sure.
I highly encourage you to check out the External Users walkthrough video Adalo Youtube | External Users and if that doesn’t help, I recommend you reach out to the Adalo | Maker Community Forum where our amazing community of Makers and Experts may be able to assist you in setting this up.
@all Does the Adalo Team know that you are having this problem? And how can I make them aware of it?
Thank you very much for contacting Adalo Support. I think I didn’t open a ticket for that bug to be honest.
To open a ticket, just fill the following form:
In the last 12 months I’ve opened couple of tickets and they ALL got solved more or later.
I hope that helps. If you open a ticket and especially if you are a paying customer, you will get the ticket solved. Nothing stayed unresolved in their pipe in my experience…
Hey everyone,
I’m using the external users feature with @xano as backend since december and so far through all tests we are currently making it works very great and was easily to implement and set up.
There is just one thing I’m comming up with and couldn’t find it in online tutorials and/or this forum and other websites. Maybe you have an Idea:
I’m securing my API endpoints with user authentication and the thing is: if a token expires e.g. after a day, the user is still logged in in the app just cant see information from the secured external collections.
Currently as some sort of a workaround I put a small 1-sec-countdown on every main screen of my navigation to check with a “auth me” call, if I get a user ID in return, which means that the currently used auth-token is still valid. If the return is empty i’m logging out the user and he has to login again.
My home screen is a splash screen that also checks if the user’s auth tokin is valid and if not: sign out & redirect to the login-screen.
As many users are not terminating the app but have it running in the background, sadly the app is not loading the “home-screen” anytime the user is coming back using the app from the background and I think my workaround of the “auth me”-call everytime a main screen is visited is very inefficient and results - with a higher number of users - in a very high number of API-Calls I want to avoid.
My question is: Is there a possibillity to log the user out after the token is expired without calling the API like a dozen times while the user is still online?
Hello everyone.
I’m about to use an external database for the first time. I’m wondering if I should store the user data in an external or internal database.
You have reported bugs here about storing user data in the external database, but are those bugs still there?
Also, I would like to know your thoughts briefly on whether I should store user data in the external or internal database, including the pros and cons of each.
There are youtube videos that show how to use external users with Supabase and Xano, or synchronize with Bubble user collections.
General understanding is if you have already an existing users database and you have other apps (beside Adalo) that will use that users database, you will need to choose externals users.
If you are doing it just to know (research), just watch those videos and follow them exactly.
If you want ease of building, stay with internal collections.
It’s been in beta since ever. I love Adalo as much as I have it!
The slow pace implementing these features drives me crazy, but that’s ok, at some point they will complete it. Not having the user collection is an issue that forces me to use workarounds, definitely not an elegant solution especially when we need user collection info for conditional logic.
Hi
I hope all are good and in good health. I am new to adalo and we are in process of integrating our custom web app with adalo mobile app. I am facing a very odd issue.
we have api’s ready which can connect with Adalo and communication is not an issue. I am facing one very odd issue which is while setting up the login it is giving us an issue.
i can successfully test the url and url is giving use the response back as expected. In the full response i am getting all the response which i am sending from the web app. But the problem is the adalo is not picking up the right fields for authentication token and user id.
Oh I see. This seems like a very limiting decision from a business stand point because some systems have there own databases and such. And when they need to or want to create an app to work with their systems already in place that really sucks. I mean they are potentially losing out one a ton of business that will now find other products.