
Search found 8 matches
- May 21st, 2013, 5:05 am
- Forum: Feature Request
- Topic: Notification
- Replies: 12
- Views: 113919
Re: Notification
Unfortunately,as of now in iOS there is no way to run code in the background of the device.
Until there is, or until xFeed offers a server based download strategy there seems little reason to set a notification on new items as the app will be running as they become available.

- May 21st, 2013, 5:01 am
- Forum: Feature Request
- Topic: Username/Password Protected feeds [Solved]
- Replies: 2
- Views: 47217
Re: Username/Password Protected feeds
Support for digest/realm protected content has been added in xFeed 4.0.
Not sure if that solves your issue, but I am an optimist and as such I am marking this solved!
Not sure if that solves your issue, but I am an optimist and as such I am marking this solved!
- May 21st, 2013, 4:59 am
- Forum: Feature Request
- Topic: Cyrillic support [Solved]
- Replies: 5
- Views: 62344
Re: Cyrillic support [Solved]
Support for many, if not all, character sets has been implemented in xFeed version 4.0. 

- June 13th, 2012, 5:51 pm
- Forum: Bug Report
- Topic: Feed's entries report wrong date [Solved]
- Replies: 1
- Views: 28741
Re: Feed's entries report wrong date
Thanks again, manco!
The version of xFeed in development first uses the date in the item as the date, if available. If it is not available, it will default to the fetched time.
Thank you for stopping by!
The version of xFeed in development first uses the date in the item as the date, if available. If it is not available, it will default to the fetched time.
Thank you for stopping by!
- June 13th, 2012, 5:47 pm
- Forum: Bug Report
- Topic: xfeed parsing crash? [Open]
- Replies: 24
- Views: 451641
Re: xfeed parsing crash? [Open]
Very interesting... thank you!
- March 24th, 2012, 6:46 pm
- Forum: Bug Report
- Topic: unable to parse. error 9 at line 17, colmn 44
- Replies: 2
- Views: 31577
Re: unable to parse. error 9 at line 17, colmn 44
Hey, thank you! Encoding and internationalization is one of the major weak points in the current version. Thank you for your input and you time investigating the issue. I know that it has been some time, however, i can assure you that there is newer versions in the works. Proper encoding and at ...
- January 28th, 2012, 2:53 am
- Forum: Bug Report
- Topic: "unable to parse" message
- Replies: 3
- Views: 33975
Re: "unable to parse" message
Thank you, Hristo. We'll get that taken care of!
- May 18th, 2009, 6:50 am
- Forum: Bug Report
- Topic: Bugs after 1.1 [Solved]
- Replies: 2
- Views: 16301
Re: Bugs after 1.1
Jorge, thank you very much for sharing this bug! It is very embarrassing that something like this fell through the cracks!
An update witch should remedy this problem has already been uploaded to Apple. Again thank you very much for finding and reporting this bug!
