All documents
Setup guide

Unblocking Sign in with Facebook

Everything on our side is built and live. Four fields in the Meta App Dashboard are all that is left, and only the app owner can change them. This is each one, photographed, with the detail that has caused two missed attempts.

Document
OPS-FB-1
Version
1.0
Date
16 October 2026
Status
Action required
Author
Abad Naseer

1What is blocking it

Sign in with Facebook is built and live on all four agents. The button appears, and pressing it sends the person to Facebook correctly. What does not happen is Facebook sending them back.

Between 13 and 16 October our server recorded twelve sign in attempts leaving for Facebook and not one completed sign in. Facebook answers every one of them with the same message:

Can't load URL: The domain of this URL isn't included in the
app's domains. To be able to load this URL, add all domains and
subdomains of your app to the App Domains field in your app settings.

OAuthException, code 191

Facebook refuses before it ever contacts us, which is why there is nothing in our logs to fix. Google sign in was configured the same way on 14 October and has worked since; nothing in our code differs between the two.

The part that has been missed twice

The Site URL was set correctly on the first attempt. That is a different field. App Domains sits above it and is still empty, and it is the one the error is about. Section 2 is that field.

2Add the app domain

Go to App settings, then Basic, in the left hand menu of the App Dashboard.

Meta App Dashboard, App settings, Basic, with the App domains field empty
Before. App domains is empty. This is the current state of the SmartZees app and the reason sign in fails. Note that Contact email and Display name being filled in makes no difference to this.

Click the App domains box, type the domain, and press Enter.

smartzees.com
This is the step that matters

After pressing Enter the value must appear as a blue tag with a small cross next to it. If it is still plain text sitting in the box, Facebook has not accepted it and saving will not keep it. Press Enter until the tag appears.

The same field with smartzees.com shown as a blue tag
After. The value has become a tag. This is what correct looks like. Anything else, including the right text typed but not entered, will not work.

Scroll to the bottom of the page and press Save Changes.

The Save Changes button at the foot of the Basic settings page
The button is at the very bottom, below the business address fields, and is easy to scroll past.

3Add the redirect address

A second field, on a different page. Go to Facebook Login, then Settings, in the same left hand menu.

Find Valid OAuth Redirect URIs, paste the address below, and press Enter so that it becomes a tag in the same way.

https://smartzees.com/auth/facebook/callback
The Valid OAuth Redirect URIs field containing the callback address as a tag
The address entered correctly. Note Use Strict Mode for redirect URIs is on just above it, which means the address must match character for character. A trailing slash or http instead of https will be refused.

Press Save Changes at the bottom of this page too.

4Check it yourself, in ten seconds

The same page has a checker, so there is no need to wait for anyone to test a sign in. It is at the top, called Redirect URI Validator.

Paste the same address into it and press Check URI.

The Redirect URI Validator showing a red cross and an invalid message
Not done yet. A red cross and This is an invalid redirect URI for this application means the settings in sections 2 and 3 have not been saved. This is what the SmartZees app returns today.
The Redirect URI Validator showing a green tick and a valid message
Done. A green tick and This is a valid redirect URI for this application. When you see this, tell us and we will test the sign in immediately.

5Switch the app to Live

While the app is in Development mode, only people listed as admins, developers or testers of the app can sign in. Everybody else is refused, even with sections 2 and 3 correct.

The App Mode toggle in the dashboard header, showing Development and Live
The toggle sits in the bar at the top of every page of the dashboard. Slide it to Live.

Facebook will ask for a Privacy Policy URL before it allows Live mode. It is on the same Basic settings page as section 2. Any public page describing how customer data is handled is enough.

6What happens next

Nothing on our side has to change. No new release, no restart, no code. The settings above take effect immediately.

  • 1You save sections 2 and 3
    And confirm the validator in section 4 shows a green tick.
  • 2You tell us
    We run an automatic check against the app, which confirms it without anybody having to sign in.
  • 3We test the sign in end to end
    The same way Google was tested on 14 October: sign in once, then confirm the session carries across all four agents.
  • 4We confirm it to you
    With the result either way.
One separate thing, worth knowing

The Meta app is currently named uplapp. That name is what customers will see on the Facebook permission screen, as Continue to uplapp. It will work, but if the name should be SmartZees, changing it is the Display name field on the same Basic settings page in section 2.

Written by Abad Naseer. Every measured number in this document is cited from the running system or from the code, and every target says that it is a target. Where the two disagree, the document says so rather than choosing the flattering one.