Google Sync Issue

  • Anonymous - 2012-05-28

    As users are reporting sync issues, I wanted to quickly post on the plans to
    resolve them: There are no plans atm. I am not able to look into this issue in
    the next days. I will post back until I had time to see whats the issue (I
    think it might be that Google changed the expiration date of access tokens).

    There are really good alternatives like FeedDemon or Reeder. Both support GR


  • jocogi

    jocogi - 2012-05-29

    Thank you for the update Ben. I appreciate you looking into the issues, and
    understand you will fix it when you have a chance! Are there any further
    details or assistance I can provide to help when you start troubleshooting?

    I have not tested Reeder, but I cannot personally recommend FeedDemon as an
    alternative. It is lacking critical features related to automatic searches,
    and I found the developer very frustrating to communicate with. RSSowl is
    vastly superior. I would even be willing to support a premium version, or
    advertising, but in the mean time I am considering donating.

    Thank you again for your time.

  • Anonymous - 2012-06-06

    I am now running one week on RSSOwl 2.1.2 with GR and dont have any sync
    issues. So its not an easy problem for me to solve...

  • jocogi

    jocogi - 2012-06-07

    Are there any details or logs I can provide to help you? I'm not very
    experienced with this sort of thing, but I would like to help in any way I
    can. I love this software so much!

  • genodeftest

    genodeftest - 2012-06-07

    A log is generated, see for
    how to export it. You may upload it and link/post it here. But I expect that
    there is need for some debugging with a real debugger and breakpoints, TCP
    package capturing and analysis (what does RSSOwl and Google Reader send), … –
    time consuming work. And I'm sorry I can't help since I don't know RSSOwl's
    details and never worked with anything related to Google Reader. See http://w
    for how to build RSSOwl which is required to debug it with Eclipse.

  • mprost

    mprost - 2012-06-07

    Just in case this may be of help to locate the issue, I have certain news
    filters set up to mark as read and label certain articles in GR, and these
    filters have started having erratic behavior recently (some articles get
    correctly labeled/marked, some others don't).

    My log appears to be full of messages like this one:

    !ENTRY org.rssowl.ui 4 4 2012-06-07 13:27:50.615
    !MESSAGE Server returned HTTP Status 400 (Bad Request)
    !STACK 1
    org.rssowl.core.connection.ConnectionException: Server returned HTTP Status 400 (Bad Request)
        at org.rssowl.core.internal.connection.DefaultProtocolHandler.internalOpenStream(
        at org.rssowl.core.internal.connection.DefaultProtocolHandler.openStream(
        at org.rssowl.core.internal.connection.DefaultProtocolHandler.openStream(
        at org.rssowl.core.util.BatchedBuffer$
    !SUBENTRY 1 org.rssowl.core 4 4 2012-06-07 13:27:50.616
    !MESSAGE Server returned HTTP Status 400 (Bad Request)

    I can post the full log if that may be of help.


  • Anonymous - 2012-07-28

    RSSOwl 2.1.4 is out with a fix for the "400 Bad Request" issue when RSSOwl
    tries to synchronize many news to GR. If you are still seeing this issue with
    2.1.4, a workaround is to limit the number of news per feed (using Properties

    Clean Up settings).


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks