Hey there! We’re aware of this issue. This is related to a system that we implemented hastily to get 0.19.0 support working; we’re working on a more robust solution for the next update. If you see this error, going back to the communities list and re-entering the feed should fix the issue.