Some Google+ accounts may experience missing reposts
Google+ API has started to misbehave recently and for some accounts the latest posts are not being returned so Friends+Me is not able to repost them.
I’ve started discussion with the Google+ team regarding this matter and I’ll keep you posted.
Thank you all for your patience.
Google+ Exporter 
Yes, I have been experiencing this a few times.
LikeLike
Ah, that explains things. Thanks for looking into it 🙂
LikeLike
Great! Keep us posted.
LikeLike
Thank you for keeping on top of this.
LikeLike
Ty for letting us know!! :-)))
LikeLike
Appreciate your staying on top of this, thanks.
LikeLike
Thanks for the update. As you know, I experienced this problem yesterday (and haven’t yet checked my other social media accounts today).
LikeLike
Did not have the problem on Sunday, however Saturday was a disaster. Reposting wasa pain!
LikeLike
Reposting seems working fine but the new posts on the Google+ acting as the source are gone missing for me.
LikeLike
Alois, can you update us through e-mail on what should we do, or when things are go back to normal? Thanks!
LikeLike
Yohanes G. Pauly there’s nothing anybody but Google+ team can do about it at the moment. You should have email response your inbox by now.
LikeLike
The problem may also by related to the Google+ account age and location restriction setting introduced recently.
So please everybody please make sure no restrictions are enabled for your G+ accounts.
This help page will help you to check the setting http://help.friendsplus.me/article/55-have-been-friends-me-skipping-your-new-posts-lately
LikeLike
Friends+Me I have triple check my Age & Location restriction setting, and it is set to Anyone from earlier. And I remember, this new setting has been informed by Google+ many weeks ago…
I noticed the problem of repost in my case is related to the usage of # hashtag for Friends+Me repost restriction. If I use # (including ), then it is not repost. When I am not using any #, it is still repost, at least yesterday.
Hope this info helps you to find solution internally. Or other users can try my hypothesis and inform back to Alois in Friends+Me so he can help us soonest. 🙂
LikeLike
Yohanes G. Pauly it really is not a problem with a hashtag routing, Friends+Me is simply not getting new posts from Google+ for your account.
Interesting thing about this all is that not all accounts are affected. Weird.
LikeLike
Still no reply from Google+ team.
LikeLike
ok, thanks for updates
LikeLike
Friends+Me No Luck Today Hit and Miss on some accounts and random on posts… no trend I can see. Any Word from the G+ Team?
LikeLike
not reposting on my end… checked audience settings, that doesn’t seem to be it…
LikeLike
I’ve finally figured out what’s wrong.
Posts returned by the Google+ API are not being sorted by time. That means new posts can be placed at the end of the list or even never returned as was happening recently. The G+ team is working on a fix.
Thank you all for your patience!
LikeLike
Friends+Me Great! Thanks for staying on top of that and keeping us informed.
LikeLike
Good to know hopefully this gets resolved soon.
LikeLike
Friends+Me Just tried to post and it died on me at a critical time. Was working all morning kicking ass and the one post that was mine and not a re-post got stuck in the ‘Q’ and did not go out to the other platforms. Bumbed out dood. ;(
https://plus.google.com/118151257740729442682/posts/8QAbNY1JPQY
LikeLike
Also affected. Subscribing comments… Will Friends+Me repost older posts once it’s fixed?
LikeLike
Still not resolved I see. Good question Ondřej Pokorný although some of mine will be out dated and of no use. I think this has been going on for a week now, a little too long.
LikeLike
Ondřej Pokorný I am afraid not. There’s problem with g+ API feed that posts are not ordered by time of the last update so new posts may appear at the end of the returned list or not at all.
G+ team is trying to fix the problem.
LikeLike
Working for me this morning, all is well with the world. Time will tell.. Thanks Friends+Me
LikeLike
Personal posts were working okay this morning, but business pages are still either not posting, or are posting with a massive delay. (just FYI, I know you’re waiting for Google+ on this one!) 🙂
LikeLike
No repost this morning
LikeLike
Any news ? …
LikeLike
Emmanuel Russeil still nothing. I’ll ping them again.
LikeLike
It’s working intermittently for me. Maybe half my posts are going through.
LikeLike
thanks
LikeLike
Would it be difficult to implement sorting of the returned activity list in Friends+Me? It’s a JSON structure, and provided their dates are consistently zoned etc, it should be “possible”, although I have no idea how your app is designed so may be more difficult than it seems?
LikeLike
James Gray problem is that even if I fetch for example last 100 activities I cannot be sure the newest ones will be present there and to fetch more may get us too close to the daily limit with so many users.
LikeLike
Ugh – I see your problem. The API is really limited too. If Google simply added the ability list posts after a particular date/time stamp rather than regurgitate up to a random 100 activities, this would practically solve our dilemma. 😦
LikeLike
Just did some poking around in the API – you can search for arbitrary strings in activities…but not dates(?!). Seriously Google, WTF? Surely date matching is orders of magnitude less difficult and resource intensive than free text search!!
LikeLike
I’ve deployed a workaround which should kind a work but it’s not a 100% solution.
I started to fetch last 50 activities and sort them on F+M side. There’s no guaranty that those returned 50 activities are the very last ones but for the time being it’s better than nothing.
LikeLike
It work fine for me today !
LikeLike
Alois Bělaška It seemed to work for the last two scheduled times on Thursday.. although the order wasa little messed up. Just sheduled first two for 3 clients today. If that works will load up a couple of days worth..
LikeLike
Awesome!
LikeLike
Alois Bělaška Friends+Me The first ones published…. now to get the rest placed. Thanks, nice working with you folks
LikeLike
Does this bug is when corrected?
LikeLike