Child Item

BadResponseException: Bad JSON: again

Jose L.8

Platform: Java
SDK/library: dropbox-sdk-java 4.0.1 (latest)

We are getting errors parsing team log contents again.

Request id: 2c56a267b7c14da5be4c49506320e667

Request id: 39fddcc390e14431ad0fd1c3adfc9116

Request id: 56c6798cb91246f4ac69d81eeef8dd37

Caused by:

com.dropbox.core.BadResponseException: Bad JSON: expected end of object value. at [Source: (ByteArrayInputStream); line: 1, column: 330017] at com.dropbox.core.v2.DbxRawClientV2$1.execute(DbxRawClientV2.java:158) at com.dropbox.core.v2.DbxRawClientV2.executeRetriable(DbxRawClientV2.java:330) at com.dropbox.core.v2.DbxRawClientV2.executeRetriableWithRefresh(DbxRawClientV2.java:351) at com.dropbox.core.v2.DbxRawClientV2.rpcStyle(DbxRawClientV2.java:137) at com.dropbox.core.v2.teamlog.DbxTeamTeamLogRequests.getEvents(DbxTeamTeamLogRequests.java:47) at com.dropbox.core.v2.teamlog.GetEventsBuilder.start(GetEventsBuilder.java:123)

...

at com.dropbox.core.stone.StoneSerializer.expectEndObject(StoneSerializer.java:98) at com.dropbox.core.v2.teamlog.EventDetails$Serializer.deserialize(EventDetails.java:35442) at com.dropbox.core.v2.teamlog.TeamEvent$Serializer.deserialize(TeamEvent.java:557)

Find more posts tagged with

Developers

Comments

Greg-DB

Thanks for the report! We'll investigate and I'll follow up here once I have an update.

Jose L.8

Hi,

opening this again as error is back.

Library is updated to v 5.0.0

Caused by: com.dropbox.core.BadResponseException: Bad JSON: expected object value. at [Source: (ByteArrayInputStream); line: 1, column: 360868] at com.dropbox.core.v2.DbxRawClientV2$1.execute(DbxRawClientV2.java:158) at com.dropbox.core.v2.DbxRawClientV2.executeRetriable(DbxRawClientV2.java:330) at com.dropbox.core.v2.DbxRawClientV2.executeRetriableWithRefresh(DbxRawClientV2.java:351) at com.dropbox.core.v2.DbxRawClientV2.rpcStyle(DbxRawClientV2.java:137) at com.dropbox.core.v2.teamlog.DbxTeamTeamLogRequests.getEventsContinue(DbxTeamTeamLogRequests.java:121)

Some request ids to look further into:

162d6ee34b2640d59343e189900cf775

1b20d77ecb054906b5528c50c14efd26

a13763fe82c249c8ac7338829fd7cf40

4bdf227c47fc4b1ba4440b2c2aecc317

Also can you confirm that 5.0.0 is last version to support Java 8? If so, these changes should go to a 5.0.x

Greg-DB

Thanks for the report. I'll raise this with the team again.

And yes, v5.0.0 was the last version before v5.1.0, where Java source and target compatibility was bumped to 11. The team applies updates to the SDK to the most recent version, but I'll pass this along as a request for support on older versions as well. I can't make any promises regarding that myself though.

Greg-DB

This issue is fixed in the latest version of the Java SDK, which is currently v5.3.0.