#1

I have been trying to connect Twitter data using TwitterAdapter. Error messages around TimeZones persists

TwitterAdapter_Error

TimeZone%20Error

Most forums point out that the time zones for both Twitter account and the Adapter Agent’s host OS should be the same.

I find that the time zone setting in Twitter account is GMT and that of my Adapter host OS is UTC.

I am wondering if the error is due to the mismatch in the time zone representations. Could that be a possible cause? Can someone help me resolve this issue?

#2

This may have something to do with Upcoming changes to the developer platform - timezone info is now private, and set to null which might break some existing code that expects a value there.

The Authentication error may also be caused by your server / machine not having time in sync (turning on an NTP service should sync it up properly, the OS timezone settings don’t matter)

1 Like
#3

Thank you so much IgorBrigadir. I turned on the NTP service and still getting the error for JSONObject for time_zone not found. My code is expecting a non null value. I will look out for the updates on the developer platform.

Thanks again for the info.

#4

You will need to patch your code to accept null values in time_zone as this field is deprecated

1 Like
#5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.