Value <?xml of type java.lang.String cannot be converted to JSONObject

[lunarok]

Hi,

I get this error message when trying to sync my feeds :
Value <?xml of type java.lang.String cannot be converted to JSONObject

[lunarok]

Sorry, not complet desc.
So in my case I have owncloud 5.0.7, last version of news app and app framework. Android app is up to date.
I'm using self signed certificate (option allo all ssl certs is enabled)

I'm running owncloud behind a lemonldap sso, but remote.php is unmanaged (and also index.php for now as I require it for owncloud bookmarks android app)

Any idea ?

[David-Development]

Thank you for the report.
What version do you use exactly ? This one ?
http://apps.owncloud.com/content/show.php/News?content=158434

Or are you up to date with the GitHub version of the news app ?.
In order to use the new android app you will need to update to the newest news app from GitHub.
News App version must be >= 1.1

The version which is available in the official ownCloud Repo doesn't support the new api yet.
I don't know when a new version of the news app is pushed to the apps.owncloud.com repo ? @Raydiation

[lunarok]

Hi,

I have update the app using the git version as you says.
(version 1.101)

But not better. When I check inside Owncloud, it still says 1.001 whatever I get the "update" button from the application management page and already click
Is there any trick to do so owncloud know what real version he has ?

[tduboys]

Hi, I've had the same issue with owncloud 5.0.7 and news app updated with GIT commit owncloud-archive/news@a5b1c63 (Wed Jun 5 12:28:10 2013)

I've updated the news app with git to the last commit, and now, the login is working.

[David-Development]

@lunarok Then I think you've done something wrong. For me it's working and I can see the correct version number as you can see in the images I've attached.

Make sure you did the following steps:
Download the following files: (On the right side there is a button download as zip)
https://github.com/owncloud/news
https://github.com/owncloud/appframework

Unzip the stuff in the following folder which should already exsists: (Via SMB or FTP or what ever you use)
Replace the existing files.

[path_to_you_owncloud]\apps\news (For the content from the news app)
[path_to_you_owncloud]\apps\appframework (For the content from the appframework app)

Then you should able to see the correct version number in your owncloud!
I hope it works for you now.

[lunarok]

I have update again, the button that appears is to put back the version on apps.owncloud.com.

So now I'm exactly in App Framework 0.101 and News 1.101.
But still get this error

[David-Development]

Okay, sounds strange. Are you using some special server setup?
Probably you can offer me a test account? Then I can check quickly where the error is.

[lunarok]

My owncloud is behind a lemonldap, so basicly to access files inside owncloud you must be logged in the SSO.
But there is some unprotected url for Owncloud :
public.php, remote.php and now index.php (as it is use by bookmarks extension and needed for sync from Android, and I think it's used for News application too)
Is it using an other url ?
Yes I can give you a test account by pm

[David-Development]

Since the new api it's using an url like this: [...]/owncloud/index.php/apps/news/api/v1-2/version
That would be great. My Email is david-dev@live.de
Thank you for your help!

[stonerl]

I get the same error when I try to connect to my ownCloud Server. Until yesterday I was using version 0.3.3 from the Play Store and had no problem connecting to my server. I installed the 0.3.5 apk from github and cannot connect.

[lunarok]

Sorry, week full, was waiting today to send you the account for test (and I test also by fully desactivating LemonLDAP on /owncloud, but not better)

I receive notification from +stonerl about the apk on github in an updated version. I install it, and for me it's all working now.

[David-Development]

@lunarok Nice to hear.
@stonerl Please update your news app and your appframework (the newest version from GitHub). Or downgrade to the android app to 0.3.3.

[David-Development]

This issue should be detected by the Android App since 0.3.6.