Old/Fixed Known Issues
Old/Fixed Known Issues[Old/Resolved] Known Issues
[Active/Recent] Known Issues
INSTAGRAM [Dec 2017]
Instagram made some very big changes in its workflow causing many major troubles.
1. “checkpoint_required” issue. It has been fixed in the plugins version 4.1.1 and API 4.0.37. Please update both plugin and API. More info about the fix here
2. “{“message”: “login_required”, “logout_reason”: 3, “status”: “fail”}” – Fixed in the API 4.0.42.
3. “{“message”: “Bad request”, “status”: “fail”}” – – Fixed in the plugin version 4.1.2 and API 4.0.39
4. “{“authenticated”: true, “user”: true, “status”: “ok”}” – Fixed in the API 4.0.38
5. “{“message”: “login_required”, “error_title”: “You Were Logged Out”, “error_body”: “Please log back in.”, “logout_reason”: 8, “status”: “fail”}” – Fixed in the API 4.0.42
6. “{“authenticated”: false, “user”: true, “status”: “ok”} “ – Fixed in the API 4.0.44
Update [Dec 18, 2017] All known issues are fixed. Please see the “Instagram issues” post for more info.
FACEBOOK [October 2017]
Please see here for instructions how to fix this error: [October 2017] Facebook Changes
Instagram [Aug 2017] – “[error_type] => sentry_block” Error
Explanation is here: Instagram – Issues
DeviantArt – Site is unstable. Many posts are getting lost.
Flipboard – Site is unstable and sometimes si throwing “Flipboard Oops, something went wrong” or “500 Server Error An internal server error occured” errors. Nothing can be done until Flipboard fixes itself.
Stumbleupon [Sept 2017] – Stumbleupon activated captcha for logins. It causes “Client version not specified” and “ValidateToken: Invalid token” errors.
Temporary solution for “Invalid token” error: Please go to the plugin’s Help/Support page and click “[Clear Cache]” button. We are working on the more permanent fix.
[Jan 2017]
Delicious – Site is unstable and sometimes is throwing 500, 503, and 301 (Moved Permanently) errors. Nothing can be done while the whole Delicious.com (del.icio.us) site is down.
[Nov 20 2016]
Reddit – Empty list of subreddits and “ERROR:” message. Fixed in the release (3.7.6)
[Aug 30 2016] Google+ – Status: Fixed on Sept 1, 2016 – API version 2.24.2.
Issue: Error (NXS): Lost Login info. Please see FAQ #3.4 or contact support .
Google switched everybody to the new Google+ interface. It caused some people “Lost Login” error. We will release new API with support for a new interface ASAP.
[May – June 2015] LinkedIn – Status: Fixed.
Issue: Some Posts to Some LinkedIn groups are missing attachment links.
[May – June 2015] Blogger – Status: Will be resolved in the next release
Issue: [Error] => Error: 404 | Invalid Login
SNAP was using “ClientLogin” authentication method for several years. As of May 2015 Google dropped support for it. https://developers.google.com/identity/protocols/AuthForInstalledApps
We will change authentication to oAuth 2.0 in the next release. Unfortunately this will require a complete re-setup of the Blogger accounts.
PS: Only “Free” plugin is affected. “Pro” plugin uses NextScripts API which is not affected by this.
[May – June 2015] Facebook – Status: Fixed
Issue: Emoji support is broken.
[March-April-May 2015] LinkedIn – Resolved in SNAP Version 3.4.17 [05/15/2015]LinkedIn is completely changing it’s API in several days (on May 12, 2015). Right now (We are assuming prior to the change) we are observing numerous different bugs and issues with it. We expect more to come, so please expect autoposting to LinkedIn to be extremely unreliable for the next several weeks.
PS: As part of the upcoming changes LinkedIn is discontinuing support for groups API, which means autoposting to LinkedIn groups using free native LinkedIN API will be no longer possible.
Update (May 12, 2015). LinkedIn changed it’s API. Groups are no longer supported. We are implementing new API/Interface right now. New SNAP version reflecting LinkedIn changes will be released ASAP.
[15 April 2015] Flipboard – Resolved in SNAP Version 3.4.17 [05/15/2015]Flipboard is actively changing it’s interfaces right now. Some users might expect interruptions and errors during the configuration and autoposting. We expect it to be fixed/finished in 2-3 weeks.
[April, 2014] Facebook Issues [Resolved – Closed][Updated May 16, 2014][Dec, 2013] Auto re-posting problems and fixes.
[Nov, 2013] Version 3 Upgrade Issues
[Nov, 2013] Version 3.0.6 and auto re-posting problem/fix.
SNAP Pro for Wordpress
Pro version upgrade adds the ability to configure more than one account for each social network and some additional features.
Latest Blogposts
Corrupted cache issue with SNAP Pro.
What happened? SNAP Pro is checking for API update every 6 hours. Today (May 22, 2019) around 6:30PM EST Google Cloud messed our update server for about 7 minutes. A bunch of "lucky" sites that were checking for update during those 7 minutes got their plugin cache...
Support for “Google My Business” is coming soon…
Support for "Google My Business" is coming this fall. Google recently made some kind of blog-a-like functionality available for local business listings. As a local business owner you can add posts, events, offers as well as products to your business listing. Although...
Facebook app review
We are getting a lot of questions about upcoming deadline for Facebook app review. People are asking what should we do. The honest answer would be: "No one has any idea". We submitted several apps for Facebook review using different ways of describing and explaining...
What happened with Facebook
What happened with Facebook? Facebook made changes to it's API access policy on May 1st, 2018. As the result we introduced our own Premium API for Facebook. We feel that we need to explain how exactly those changes affected SNAP. Since the beginning Facebook native...
Instagram issues
Instagram made some very big changes to authentication process. About 70% of our users are affected by them. Before the changes the process was quite simple: Sometimes Instagram decided that login from SNAP is "unusual" and asked for confirmation. You just had to open...
SNAP for Wordpress
SNAP for Wordpress MultiUser
SNAP API
