3.001: Expected BEGIN_ARRAY but was Number at line 1 column 19

[BernhardPosselt]

Hi David,

I'm trying to access the API on master (news + owncloud) but I'm getting the above mentioned error message. There is no stackstrace and it's kinda hard to debug. Is there some kind of debug mode?

I've made some changes to the controllers but the API should be the same. I'm unsure where the error lies but I think its some kind of JSON parsing problem? I've checked the JSON output and everything is valid and looks according to the spec (I may have missed something though), so maybe you've got some time to do some debugging, meanwhile I'm stranded and cant update my feeds on my android device xD

PS: You need this PR to fix basic auth: owncloud/core#11158

[BernhardPosselt]

I've cleared the cache and deleted the folder in my sdcard directory fyi

[BernhardPosselt]

API should also be testable on 7 btw, the interface will looked a bit fked up though :P

(that is if you reduce the owncloud min version from 7.8 to 7 in appinfo/info.xml)

[David-Development]

Thank you for the report. I tried to update my ownCloud to 7.0.2 but it sucks and after trying to pull the latest version from the git repo I'm only getting a {"data":{"message":"Token abgelaufen. Bitte lade die Seite neu.","error":"token_expired"},"status":"error"} error message.. So what's the proper way to install oc 8 from git?

I already cloned core, 3party and the news app. And I applied the pr (https://github.com/owncloud/core/pull/11158/commits) but without success..

[BernhardPosselt]

Check the dev docs, there should be a setup guide. Ttyl not home ;)

[David-Development]

Okay I think I figured out the problem. You changed the field order of the json result. (Feed Response)

Expected:
{
"feeds": [],
"starredCount": 0,
"newestItemId": 0
}

In Version 3.002:

{

"starredCount": 0,
"feeds": [],
"newestItemId": 0
}

[BernhardPosselt]

I see, thanks :)

Can you fix this? It shouldn't depend on the order but access it by key, otherwise it's very likely to break again in the future

[David-Development]

I can try to fix this issue but it's not that easy. Yes of course it should access the values based on the key but I'm using a special mechanism to read the json result (read directly from the input stream) and so it's not that easy like json.getJsonArr("feeds");

[David-Development]

Fixed ;)

[BernhardPosselt]

How did you fix it :)? I think its better to read it reliably than fast, the biggest issue with speed is the API and the amount of requests anyways, so this needs to be optimized :)

[David-Development]

Sure but the problem is that the result may be so big, that the available memory of the device is not enough (OutofMemoryException - already got this issue on older devices with the default android json reader which parses the whole result first).

[BernhardPosselt]

wow damn :) I see its a memory issue