Facebook Said Connected And Meant Nothing Of The Sort

I have written a few of these now about failures that stayed quiet. This one was louder than quiet, it was confident. The settings page did not hedge. It showed Facebook, a green badge, the word Connected.

None of it was true in the way that mattered.

What the badge was actually describing

When you connect Facebook to PodGlue, you are not really connecting your profile. Posting to a personal Facebook profile is something the platform simply does not allow software to do, and has not for years. What you are connecting is a Page, the thing with a name and followers that exists to be published to.

So the connection needs two pieces: which Page, and a key that works for that Page specifically. A key for your profile will not open your Page. They are different doors.

We were storing the profile. Both pieces, wrong. And then reporting success.

Why it slipped through

Facebook has two ways of telling an app which Pages it is allowed to touch, and which one applies depends on how the app asks for permission. We changed how we ask a couple of weeks ago, for good reasons, the new way is what finally made Facebook show a proper Page chooser during setup.

What I did not notice is that the new way also changes where the answer lives. We kept asking the old question. The old question now returns an empty list every time, no matter what you picked.

An empty list is not an error. Nothing failed. So the code shrugged, fell back to the profile, and wrote it down as a success.

The part I keep turning over: there was already a guard for this. Someone, me, had written a check that refuses to save a connection with no key at all, precisely because a broken connection that looks fine is worse than one that visibly fails. It did not fire. There was a key. It was just a key to the wrong door, and the guard only knew how to ask whether a key existed.

What changed

The code now asks the question that has the answer in it. Your permission grant itself names the Pages you approved, so we read it from there, then fetch each Page's own key.

Three things came out of that:

It refuses to lie now. If setup comes back with no Page you can publish to, PodGlue says so and saves nothing, with Facebook's own explanation attached. No green badge over a dead connection.

Errors stop disappearing. The old code turned any Facebook error into an empty list, which is how a real problem became a silent shrug. Errors now come back as errors.

You can connect more than one Page. This was the part I actually wanted. Setup shows every Page you approved, name, picture, follower count, and you pick as many as you like. A show Page and a personal-brand Page are different audiences, and they were never meant to share one slot.

What I took from it

A check that asks "is something there?" is not the same as a check that asks "does this work?" The first one is easy to write and feels responsible. The second is the one that would have caught this on day one.

I would rather PodGlue tell you it could not connect than tell you it did when it didn't. A connection badge is a promise about what happens later, when an episode goes out on a Tuesday and you are not watching. It should only be green when that promise is real.