Yeah, it’s pretty much safe, I guess, but the name is fine too, thanks.
So, you have reached the users limit for the default 8base auth profile (it is 5 for the free plan).
Your implementation is alright as I see from my quick review. Just clear Users’ table records and try to sign up again.
but i didnt delete them using a mutation, I can bearly get that thing to work. i dont understand. so now…can i send this mutation from within 8base explorer?
Im sorry i dont have the ability to do this. I dont understand. where are these users?
I linked the explanation earlier: https://docs.8base.com/docs/8base-console/graphql-api/mutations/#delete-vs-destroy
There are soft and hard delete in 8base. You execute soft one when deleting records from data builder interface. Deleted records are still in DB till they are hard deleted. You can use withDeleted: true argument to see soft deleted records:
I understand the explanation in the docs. but i dont understand from where I send the destroy mutation. and how to filter, i havent learnd that part of graphql yet. do i need to write a function with the mutation in my frontend that destroys the users just so I can start over? or can I send the destroy mutation from the graphql explorer inside 8base?
Ok.
You can use our API Explorer straight from your workspace (in fact you can use any client for sending POST request to your API like curl, Postman etc).
Here is the step-by-step guide:
You get the ids of users, executing usersList mutation
Execute userDestroyByFilter mutation passing the ids of these records or using other predicate like is_not_empty - it will destroy all the records which ids are not null
You can use auto-generated documentation for your API or Explorer feature to learn more about available queries/mutations and build it with the right syntax.
thanks. I did it. they are gone. still cant signup/login. but i dont understand why there isnt an automatic user called “owner”. doesnt this make sense to have this from the start?
I suppose you are losing your email somewhere in the code.
Can you try to execute userSignUpWithPassword mutation straight to your API endpoint?
Postman example:
then i also tried after this to send a post with a bad authProfileId, on porpoise, just to see what happens, and it returned right away saying “AuthenticationProfile not found”
so this means that it does go to 8base and try to post. and the authProfileId is good. its something else. maybe the profile itself
now i tried again and got : “Unexpected error value: { code: “UserLambdaValidationException”, name: “UserLambdaValidationException”, message: “PreSignUp failed with error The limit is reached for metric ‘appUsers8base’…” }”,