FormatException: Unexpected end of input (at character 1)

[RoonMoonlight]

Checklist

• I am able to reproduce the bug with the latest version.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug, that only occurs in Squawker

Affected version

v3.6.2+300012833

Steps to reproduce the bug

1. Go to random profile page
2. Displays FormatException: Unexpected end of input (at character 1) (excluding Follower/Following tab)

Expected behavior

It should be able to see Tweets/Post without issue

Actual behavior

It returns error

Screenshots/Screen recordings

Logs

N/A

Affected Android/Custom ROM version

Android 14 / One UI 6

Affected device model

Samsung Galaxy S22+

Additional information

N/A

[adsarwal]

I have the same error when I view individual subscriptions. Feeds and groups work as expected.

[imustd]

Same error, Feed is also not working for me.

[j-fbriere]

It was working perfectly well earlier today (and all the days before).
Yet another change by Twitter/X API... (sigh)
I'll look into it.

[feijoey]

It might be related to the new "highlights" feature on profiles?

[j-fbriere]

Just checked and it's the same type of problem that appeared recently where the "old" (v1.1) Twitter/X API calls for feeds and searches stopped working suddenly.
I guess Twitter/X is has finally decided to abandon the support of all v1.1 API requests. Oh well.
It may take a bit because I have to implement the new types of requests for the Profile.

[SendPatches]

For now couldn't we just use tweet search
EDIT: I'll be working on making a pull request ASAP to fix this

[RoonMoonlight]

For now couldn't we just use tweet search

Good news: nitter.net still works well, use it in the meantime

[SendPatches]

Just created a draft pull request #166

[SendPatches]

I'll work on fixing the last few things + code refactoring before I get it ready for review

[SendPatches]

Pull request ready to be merged

[SendPatches]

I've added apks to the pull request for those that want to test it

[j-fbriere]

@mrhcjones thank you for this "quick fix" which is a workaround using the Twitter/X API requests already implemented in Squawker.
As you know this fix uses the same type of Twitter/X API request that the one used for the feeds/groups and the searches (users/tweets), which are very rate limited (50 requests per 15 minutes).
So any request to a profile will directly impact the rates for the feed/groups requests that already very rate limited (and inversely).
That is the reason why I'm reluctant to merge this fix.
The actual type of Twitter/X API requests that must be implemented for the profile, which are different types of Twitter/X API requests, are far less rate limited (500 requests per 15 minutes) and also will not impact the feed/groups/searches requests.

[SendPatches]

@mrhcjones thank you for this "quick fix" which is a workaround using the Twitter/X API requests already implemented in Squawker. As you know this fix uses the same type of Twitter/X API request that the one used for the feeds/groups and the searches (users/tweets), which are very rate limited (50 requests per 15 minutes). So any request to a profile will directly impact the rates for the feed/groups requests that already very rate limited (and inversely). That is the reason why I'm reluctant to merge this fix. The actual type of Twitter/X API requests that must be implemented for the profile, which are different types of Twitter/X API requests, are far less rate limited (500 requests per 15 minutes) and also will not impact the feed/groups/searches requests.

I understand, I'll keep the pull request open as a temp workaround for now