🗑️ Fixed: removing friends looked like it worked and did nothing
- Deleting deactivated friends failed every single time, for every profile, and had done for weeks. The screen said it was done, the names disappeared from the list and the count dropped, but Facebook was never touched. The next scan fetched them straight back from Facebook and there they were again.
- Deactivated accounts are stored differently from normal friends: they carry no username. Removal has two routes and the missing username closed both, so the removal step reported "0 removed" every time. The part that made it invisible is that nothing read that answer. The list was rebuilt with every ticked name taken out regardless of what Facebook had actually done.
- The account number was sitting in the record the whole time, just encoded, so removal now recovers it and drives Facebook through the profile that number opens. It was verified against real deactivated friends rather than assumed to work.
- The same defect was found on two more screens, Inactive Friends and Friends With Engagements. "Remove Selected" there also dropped every ticked row from the table and from your saved list whether or not Facebook confirmed anything. All of them now keep a person in the list when the removal did not go through, and tell you it was a partial failure instead of quietly claiming success.
🔒 Fixed: Safe Lock was not protecting anyone on Inactive Friends
- Safe Lock exists so a friend you tick as safe is never removed. On the Inactive Friends screens it was not doing that. The tick updated what you saw on screen, but the list the removal actually runs from was never updated, so a safe-locked friend could still be put through removal.
- Tested directly: before the fix a safe-locked account was attempted anyway alongside an unlocked one. After the fix only the unlocked one was attempted.
- A related bug on both screens could silently drop the last row you had selected, so the number of people processed did not always match the number you ticked. Both are fixed, and the progress count now comes from the same list the removal uses.
👥 Fixed: Group Remover removed groups from your list that it had not left
- Selecting groups and removing them cleared every one of them from your list immediately, before Chrome had even opened, and regardless of whether leaving the group actually succeeded.
- That group list is shared with Group Inviter, Member Friender and Manage Group Members, so a group wrongly dropped disappeared from three other screens too.
- Group Remover now confirms each departure by re-reading the group afterwards, removes only the ones it can prove it left, and reports the rest. If two of two could not be removed, it now says so instead of showing an empty list.
📊 Fixed: a post that failed to load counted as a post with nobody in it
- When scanning posts for engagement, a post Facebook never served was treated as a post with zero people rather than as a failure. Scan five posts, have three fail to load, and you would get "Broadcast List Created!" over an audience built from two, with nothing telling you anything was missing.
- The "N posts failed to scan" notice already existed for exactly this, but it could never fire, because nothing was ever counted as failed. That truncated list was then what got messaged, and the missing prospects were simply gone.
- This is easy to hit by accident: a typo in a post URL, a deleted post or a slow feed all land in the same place. Failures are now reported properly and the notice does its job.
Questions? Reach out anytime at support@prospectorproducts.com