We are in the process of finalizing the migration from the Google Reader back end to the new feedly cloud backend. This is an important post to help you prepare for the final step.
It is important that you run version 16 of feedly on all your devices.
On Chrome, go to chrome://extensions then select developer mode then click on update extensions to force the upgrade to the latest version.
On Firefox and Safari, you can go to http://www.feedly.com/index.html and manually re-install the app and restart the browser. The latest feedly desktop number is 16.0.515.
On iOS and Android, it is important that you go to the App Stores and make sure that you have the latest update. If you are not sure, you can un-install the app and re-install it. The latest android version is 16.0.5. The latest iOS version is 16.0.1.
Sync’ing via the cloud
Over the next 2-3 days you should expect to receive a green banner message (desktop) or a green card (mobile). This is the notification that your feeds and categories and up to 1,000 starred items have been successfully migrated to the feedly cloud and the articles you are seeing are coming from the feedly service.
It is important at that point that you restart the app on all your other devices so that they all connect to the feedly cloud.
The one part we did not migrate from google reader is your history (too much data) so you have to expect that you are starting from a blank history and your unread counts will be reset. This is a one time issue.
In some cases, there might be a gap of a few days in the saved items because migrating a few million accounts takes a few days. We have done our best to minimize that gap but we apologize if you are missing a few saved items. This is a one time issue too.
How do I login to my feedly cloud account?
To simplify the transition, we are going to continue to use Google Authentication to let you access your Feedly Cloud. We will be adding support for Twitter, Facebook, Tumblr and LinkedIn shortly.
How do I know which backend/version I am running?
If you visit cloud.feedly.com/#console you should see a list of data about your system.
This information should tell you if you backend is Google Reader or the feedly cloud and it should tell you which version you are running. The latest version is 16.0.515. If you are not running that version, see the first step to manually upgrade.
When will I get upgraded?
It is a random rolling update. Our goal is to migrate all the existing users between now and June 21st.
I can not add or load a specific feed?
This could be due to a bug in our new feed fetcher component. Feeds come in a lot of different flavors and despite trying to be very flexible and forgiving, there are some feeds we might not be able to parse. If you run into one of them, please send an email to firstname.lastname@example.org with [feed] in the title and the complete feed URL in the body of the message and we will have one of our engineers debug that feed and see why we are not able to parse it.
I see delay in some feeds getting refreshed. Why?
We are fetching about 20 million feeds every day. We have the horse power to fetch 100 million. But some of the domains we are connecting to do not know feedly yet and might throttle us. It is the case of live journal for example. We are working hard to get whitelisted. You can help by contacting the source and asking them to whitelist feedly fetcher.
We also have real-time connections to 7million feeds so updates should be generally very very fast for the most common sources.
Are there known bugs?
We are listening actively to the email@example.com and monitoring the issues which are being reported and pushing out updates everyday to address the bugs which are being reported. Here are a few known bugs. The iOS ones are going to take 7-10 days to fix because of the Apple approval.
- If your read/unread counts are aout of syn please make sure you are running the latest version of feedly on all your device. To do so please log out of feedly, re-install feedly on all your devices and log back in. Also if you have an Android phone, please clear your cache!
- If you have a category which is using the “Magazine” view, it will load a black screen. Reported by Anthony Scundi. Fixed in 16.0.512
- A couple of users have reported clicking on a category and not seeing articles displayed despite the unread count being > 0. If you have this problem, please email us using the bug report section, we are trying to understand this issue. Fixed in 16.0.512
- Feedly integration with twitter is broken. This was due to the recent twitter API upgrade. Fixed on desktop 16.0.512 and Android 16.0.5. Still broken on iOS. Use buffer as a work around.
- When you have more than 10 tags, the tags popup shows a scroll bar but scrolling makes the popup disappear. We are able to reproduce this problem and are working on a fix. Fixed in 16.0.513
- Keep unread is broken on the desktop. We understand this problem. Working on a fix. Fixed in 16.0.513
- In the All page, the unread count at the top does not get updates as the articles are marked as read. We are able to reproduce this problem and working on a fix. Fixed in 16.0.514
- Mark all as read, mark category as read, mark older than one week as read are slow and error prone. They require a manual refresh. Fixed in 16.0.514
- shift+m should mark the current page as read and move the next section Fixed in 16.0.515
- Editing feeds changes are not recorded by the server. Fixed in 16.0.515
- Some users have trouble un-saving some of items which where saved during migration. We are able to reproduce this bug and are working on a fix.
- Feedly 16 on Android 2.x has a article rendering issue due to custom fonts. We understand this problem and are working on a fix.
- The list of categories is not properly sorted on iOS and Android when the app is first started. Work around is to pull to refresh. We are working on a fix.
- On iOS and Android, the mark as read cards do not transition to the next section. We are working on a fix.
- One user reported that only 7 of her 30 feeds migrated from Google Reader to the feedly cloud. Here again, if you have this problem, contact us, we want to understand more.
- The Android widget is being migrated from Google Reader to the feedly cloud. It will come back in v17.
- Feedly does not work on Safari 6.1 beta and Safari 7.0 beta. We are aware of this and are working on a fix. Coming soon.
We will be updating this document live as new issues are discovered and existing issues are getting resolved.
The entire team has been working close to 24×7 over the last 60 days to prepare for this migration. We are listening and happy to help make this transition as seamless as possible. If you are experiencing an issue or have a question, please send an email to firstname.lastname@example.org
If you are reporting a bug on the desktop, please include the content of http://www.feedly.com/home#console and screenshots if it helps explain the problem.
Help Spread the Word
Please help us spread the word: if you see other users who have questions regarding feedly or bugs, please point them to this document. We have a few million users to migrate in less than a week, you can help. #teamfeedly
(And thanks for all the positive tweets. It is great to know that the migration was seamless for the big majority of users)
16.0.512 – 06/16 – Chrome/Firefox/Safari. Category magazine view. Twitter integration.
16.0.513 – 06/17 – Chrome/Firefox/Safari. Keep unread. Firefox custom fonts. Tagging.
16.0.514 – 06/17 – Chrome/Firefox/Safari. Mark as read bug fixes and optimizations.
16.0.515 – 06/18 – Chrome/Firefox/Safari. shift+m, subscription editing bug fixes.