I have a list of all users and two text input fields on a page. One text input is looking for users’ emails and the other is for their temporary password. The list then has two filters
Their email is equal to the email input on the list page
Their temporary password is equal to a temp password input on the list page
However, if both fields are blank the list shows all possible users, once you enter a character into the email field the email input filters work accordingly. The same goes for the temp password filter. However, it seems that despite the ‘and’ logic the two filters are operating independently and are not jointly conditional
One thing to keep in mind with this method and if you’re planning on publishing to the AppStore, Apple doesn’t like when the button disappears. I’m currently seeking another way to do this.
oh no, have you had any luck finding another solution? It’s so frustrating that I can’t create users by API. It’s the final hurdle and one I honestly never expected to cause me such a headache
Change permission to everyone as stated in the link
Create a custom login form with the button in a list pointing to all members
In that button have 3 actions, Log the user in > a Link to the new password screen > link to Home Page
If the new user’s Temp Password is not equal to zero, force them to the Create new password screen, otherwise bypass and go straight to your landing page
I have found a workaround but the filtering acting incorrectly is stopping it from working.
Rather than have the button disappear on the temp password page, have it redirect to a validator page. On this page, there is a list of all users that match the input components from the temp password page. That list also has a 3-second countdown and when the countdown is complete it automatically pushes the user to a create password screen.
If there is no match, the list won’t appear, revealing a back button that is hidden underneath it, allowing the user to try again.
This method works apart from in my instance the list filter is acting as an ‘or’ rather than an ‘and’.
I see, but how are you able to communicate this password to them, are you manually emailing out the password? My app has quite a large waiting list 1000+ so manual isn’t feasible for me
Just in case: it is not recommended to use conditional actions after sign-up or login, as they may not work correctly.
There were quite a few threads on the forum about this (dating back to 2020).
Please. This has been discussed numerous times on the forum. Sometimes conditional actions after login works, and in some time they start glitching.
The probable reason for this is that user is not “fully logged-on” after these actions. So he needs to be sent to another screen, where you can do all conditionals.
I’m using SendInBlue to issue emails.