You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TwitterApi.tweets().searchStream().execute() throws 400 error with no response body if additional parameters are included
Expected behavior
defining the call as
Integer backfillMinutes = 1;
OffsetDateTime startTime = OffsetDateTime.parse("2022-10-01T18:40:40.000Z"); // OffsetDateTime | YYYY-MM-DDTHH:mm:ssZ. The earliest UTC timestamp from which the Tweets will be provided.
OffsetDateTime endTime = OffsetDateTime.parse("2022-10-14T18:40:40.000Z"); // OffsetDateTime | YYYY-MM-DDTHH:mm:ssZ. The latest UTC timestamp to which the Tweets will be provided.
Set<String> tweetFields = new HashSet<>(Arrays.asList("conversation_id", "author_id")); // Set<String> | A comma separated list of Tweet fields to display.
apiInstance.tweets().searchStream()
.tweetFields(tweetFields)
.backfillMinutes()
.startTime(startTime)
.endTime(endTime)
.execute();
enables the additional functionality of those fields within the searchStream.
Actual behavior
when .execute() is called, a 400 APIException is thrown with a null message body
Steps to reproduce the behavior
As per the code above will reproduce this error.
It is also discovered that .tweetFields() does not trigger this error, as does excluding all optional fields.
The text was updated successfully, but these errors were encountered:
TwitterApi.tweets().searchStream().execute() throws 400 error with no response body if additional parameters are included
Expected behavior
defining the call as
enables the additional functionality of those fields within the searchStream.
Actual behavior
when .execute() is called, a 400 APIException is thrown with a null message body
Steps to reproduce the behavior
As per the code above will reproduce this error.
It is also discovered that .tweetFields() does not trigger this error, as does excluding all optional fields.
The text was updated successfully, but these errors were encountered: