XPoster offers a couple of options to help with debugging.
Debug Service Connections
If you’re having trouble connecting to one of the social media services, enabling this option will dump the server responses in the admin when you connect. This is likely to only be useful for developers or when getting support, but it may help you identify the source of a connection problem.
Enable XPoster Debugging
When enabled, XPoster debugging saves various steps in the process of identifying a post for a status update, constructing the status update, and sending the update. These steps are logged to the post meta on the post that’s being shared.
If something is not being posted correctly, or is using something other than the template you expect, this can be a way of isolating what’s happening.
The debugging logs are not necessarily easy to understand – they aren’t intended for daily consumption. In the portion expanded in the image above, what you’re seeing is the log initiating a status update: it’s determined that the status update should be sent for this already published post.
It then reports the default from your settings (which is to not send, in this case).
It informs you of the publication method: instant, means that it was a direct edit, and not scheduled or imported; and the specific WordPress filter that was executing when this was checked.
There are about 30 or 40 separate steps that can be logged, depending on the specifics of the service, type of post, and content of the post, so it’s a way you can get a lot of information if you’re having trouble.