JSON Parse Error when syncing with Commafeed.

[neo269]

Describe the bug
When FeedMe is used to Sync with CommaFeed (commafeed.com) using 'FeverAPI' it gives following error
'JSON parse error'

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Self Host'
2. Click on 'FeedMe' > enter details as follows

Host https://www.commafeed.com/rest/fever/user/XXXXXXXX
username: my_username
password: API key

3. Click on Login
4. See error > 'JSON parse error'

Expected behavior
Login into FeedMe app & it starts syncing feeds from Commafeed

Screenshots

Device info

• Device: S21FE
• OS: Android 14
• Version: OneUI 6.0

Additional context
My Discussion with Commafeed Developer: Athou/commafeed#1335 (reply in thread)

[seazon]

Thanks, I will check it.

[seazon]

I can't log in with my username and api_key.

[neo269]

I can't log in with my username and api_key.

@seazon
I have entered following details in Fever Section of the App.
Host: https://www.commafeed.com/rest/fever/user/XXXXXXXX
username: username
password: API key

I can see my feed list in FeedMe app but nothing is getting synced.

[neo269]

As per @Athou of Commafeed

The problem may be that the entry ids on commafeed.com are much larger (e.g. 34220073284). It may be that the internal database of those apps are unable to store such large numbers.

@seazon pls do help in solving this. Thank you

[neo269]

As per @Athou of Commafeed

The problem may be that the entry ids on commafeed.com are much larger (e.g. 34220073284). It may be that the internal database of those apps are unable to store such large numbers.

@seazon pls do help in solving this. Thank you

hello @seazon any update on this please? thanks

[neo269]

Hello, @seazon,
Will it be possible to repair the bug?
want to desparately use CF on other apps like FeedMe.

Thanks

[seazon]

@neo269 Thank you for your persistence. I seem to have missed your previous two replies. At present, I have addressed the cause of the problem and I will fix it in the next version.

[seazon]

@neo269 please try 4.3.6

[neo269]

@neo269 please try 4.3.6

The issue is solved. Appreciate your efforts!
Thank you!