dyerware
Support => iPad and iPhone Apps => Topic started by: xspeed on July 15, 2012, 09:05:44 AM
-
Hi,
i have trouble syncing articles properly with google account.
receiving unread articles with google account works perfect.
after reading with feedHopper or Flitter i mark my feeds as read.
the small activity indicator appears shortly in the status bar.
but at googles website all articles are still unread.
this happens with feedHopper and Flitter.
the first sync worked with no problem.
but after a few syncs it doesn't sync properly anymore.
Anybody else having this problem?
iOS 5.1.1 // feedHopper 5.2.3 // Flitter 3.0.1
-
Hmm. Let me take a look and get back to you
Sorry for the trouble
-
I read an article in fH and seeing it automatically marked as unread on the reader web page.
If I mark the feed as all read in fH, it appears all articles are correctly marked as unread on the reader web page.
BUT
I do see a problem reading articles on the web page and clicking on refresh on the feed in fH (where it should mark the articles as read by paying attention to the read state during refresh).
Is this the problem you are seeing? Or are you seeing a problem with iPad->Reader on marking things read?
thankx
-
Hi,
Or are you seeing a problem with iPad->Reader on marking things read?
exactly
feeds that i marked as read in feedHopper or Flitter are not marked as read on google reader web page.
i posted a video:
http://vimeo.com/45855174
actually i don't read articles at googles reader page.
it's just to keep feedHopper and Flitter in sync on my idevices.
with a few hundred articles a day i don't want to read all twice.
thanks
-
I see what you are doing and your intended use should work.
Thanks for the video. Btw if things worked rigt you would. It have to mark the feed read. Just reading the article sends the MSG to google for that article in real time
Just In case there is something about the feed that is confusNg our engine can you post the feed URL?
Also another thing you can do is view the activity log in-app. It's need the support menu. Read an unread article and see if an error log appears
In the mean time you have given great info. Many thanks
-
Ok I have found there are occasional sql errors when updating the database. This will prevent appropriate marking of the article as having been read.
I have made some adjustments and have not experienced an error. Though I must admit I need to beat on it more.
You are welcome to beta test it if you have the time. Our betas are installable OTA. Just let me know.