Members cannot sign in
Sign-in that works on the web and fails in the app is nearly always a configuration difference rather than a credential problem.
Which sign-in screen did you place
Section titled “Which sign-in screen did you place”There are two, and they need different endpoint groups.
| Feature | Backed by | Endpoint group |
|---|---|---|
| Login | Ultimate Member | Authentication |
| Default Login | WordPress core | Default Authentication |
Placing Default Login and enabling Authentication is a common mismatch, and it fails exactly like a wrong password.
The Ultimate Member login form is not visible to the API
Section titled “The Ultimate Member login form is not visible to the API”If you placed Login, the Ultimate Member login form needs Show this form to REST API ticked, like any other form. Without it the screen has no fields to render or submit.
Turnstile is half configured
Section titled “Turnstile is half configured”If you enabled Cloudflare Turnstile, both halves of the pair must be present:
- The site key is compiled into your app.
- The secret key stays on your site and verifies the challenge.
With the site key only, the challenge renders and verification fails for everyone. Set both under Memberside → API Keys. See Connection and API keys.
A role allow-list is refusing them
Section titled “A role allow-list is refusing them”Default Login and Default Register can restrict which WordPress roles may sign in. A member whose role is not listed is refused with valid credentials.
Check the feature’s settings before assuming the account is wrong.
Social sign-in fails only in the built app
Section titled “Social sign-in fails only in the built app”It works in the preview and fails on the phone. This is the signing fingerprint.
Native Google sign-in is authorised against your app’s signing certificate. The builder shows the SHA-1 in the social sign-in settings, and it must be registered with your OAuth client.
It changes when the signing certificate changes. See Android signing.
Signed in, but screens still look signed out
Section titled “Signed in, but screens still look signed out”The sign-in succeeded and the session is not reaching the screens.
- The Users endpoint group is off. The app cannot read who it is, so every personal screen behaves as though nobody is there.
- The app is an old build pointed at a site whose namespace changed. The
plugin moved to
memberside/v1in 2.0.0 with no alias, so apps built againstum/v1cannot authenticate at all. Rebuild and redistribute.
Registration succeeds and the member cannot then sign in
Section titled “Registration succeeds and the member cannot then sign in”Usually a WordPress-side rule rather than an app one:
- The member’s role requires admin approval before sign-in.
- Email confirmation is required and has not been completed.
Both are Ultimate Member settings, and both behave the same way on the web. Check the account’s status in WordPress.