Choosing providers
Setting a provider up on your site makes it available. Picking it on a feature is what puts its button on a screen. These are two separate steps, and a provider that is configured but never picked appears nowhere.
Four features offer the picker
Section titled “Four features offer the picker”| Feature | Stack |
|---|---|
| Login | Ultimate Member |
| Register | Ultimate Member |
| Default Login | WordPress core |
| Default Register | WordPress core |
Open the feature’s settings in the builder and pick the providers you want. The choice is per feature, so your sign-in screen and your registration screen can offer different sets — though there is rarely a reason for them to.
Social Connects has no picker on purpose. It lists whatever your site has configured, because its job is to let a member manage every account they have linked, not a subset you chose.
A provider needs both halves
Section titled “A provider needs both halves”A button appears only when the provider is picked on the feature and configured on your site. Either one alone shows nothing:
| Configured on the site | Picked on the feature | Result |
|---|---|---|
| Yes | Yes | The button appears |
| Yes | No | Nothing. Available, but not offered here |
| No | Yes | Nothing. The site omits providers with no credentials |
The second row is the one that wastes an afternoon. Nothing warns you, because picking a provider you have not set up yet is a reasonable thing to do in the order most people work.
Offer Apple, or the App Store rejects the build
Section titled “Offer Apple, or the App Store rejects the build”The builder warns as soon as you pick a provider without Apple, and the readiness audit reports it as a blocking failure before you export a listing. Both exist so the rejection does not arrive from Apple instead.
The rule applies to iOS. It does not apply to a build you only ship on Google Play, but offering Apple on both costs nothing and keeps one configuration.
Ordering
Section titled “Ordering”Buttons render in the order the registry declares, not the order you pick them — Google first, then Apple, then the rest. This is deliberate: the two providers with native in-app sign-in are the two most members will use, and they should not move around between your screens.
Members can lock themselves out
Section titled “Members can lock themselves out”A member who registered through a provider never chose a password. If they later disconnect that provider from Social Connects, they have no way back in.
If you place Social Connects, place Settings too, so the Password tab is reachable.
When it does not work
Section titled “When it does not work”| Symptom | Cause | Fix |
|---|---|---|
| The picker is not in the feature’s settings | That feature has no picker | Use one of the four listed above |
| A picked provider shows no button | It has no credentials on the site | Set it up under Memberside → API Keys |
| The Apple warning will not clear | Apple is not among the picked providers | Pick Apple on the same feature |
| Buttons appear in the preview but not the app | The build predates the change | Run a new build |
| Every button vanished after a site change | The Social Login group was switched off | Enable the endpoints you need |