Continuous crash in the application after updating it

Question

Continuous crash in the application after updating it

Closed this issue 5 months ago · 24 comments

Describe the bug
Since the last update of the Feedme application, I have continuous crashes with the application when reading articles.

To Reproduce
Steps to reproduce the behavior:

Go to app and read feed
Click on article and crash
Continuous closures and freezing of the application.

Screenshots

Device info

Device: Google Pixel 7 pro
OS: android 14
Version: 14

Additional context
Do not hesitate to request what you need to help correct the problem.

Answer 1 · 2024-07-04T12:52:25.000Z

I do have the same problem on Pixel 7, but I cannot reproduce it at the moment, because I marked the whole feed as read to read the other feeds.

Answer 2 · 2024-07-05T09:02:11.000Z

I have the same problem, and most time it will crash at the first article or the last
v4.2.3 and v 4.2.5 are the same.

Update: I reinstalled v4.2.2, and everything is ok now

Answer 3 · 2024-07-05T23:59:36.000Z

Can you please quickly check if 4.2.5.1 fixes the version? Since I can't reproduce it.

Answer 4 · 2024-07-06T06:03:17.000Z

I had the same issue with v4.2.3 on a tablet and usually the app crashed after reading the first article. After installing v4.2.5.1 it looks good after the first test.
Thanks for the fix and the great app.

Answer 5 · 2024-07-06T07:33:30.000Z

@mdino-gh good news. Hope I found the root cause.

Answer 6 · 2024-07-06T22:28:01.000Z

Can you please quickly check if 4.2.5.1 fixes the version? Since I can't reproduce it.

Hello, in the new version the error continues to appear. I was reading articles and it app crash again.
How can I detect why it is crashing?

Answer 7 · 2024-07-07T01:17:50.000Z

@juanico10 reproduce crash and goto feedme - settings - about - feedback, feedme will attach the error log.

Answer 8 · 2024-07-07T01:41:02.000Z

Can you please quickly check if 4.2.5.1 fixes the version? Since I can't reproduce it.

@seazon I installed v4.2.5.1 and used for a day, it doesn't crash any more.

Answer 9 · 2024-07-07T18:51:15.000Z

Unfortunately version 4.2.5.1 crashed again after a while. So I installed 4.2.6 and the app also crashed. I de-installed the app and installed v4.2.6 again and restored my configuration. The logfile size was already 15 MBytes after using FeedMe for over 3 years on this device. I briefly checked the latest entries, it looks as the app isn't able to write to the log when it crashes.
For now it looks good.

Answer 10 · 2024-07-07T21:15:00.000Z

@juanico10 reproduzca el fallo y vaya a feedme - configuración - acerca de - comentarios, feedme adjuntará el registro de errores.

Hello,

I attach several reproductions of the application crash.:

error.log
error (2).log

Best regards.

Device:google Pixel 7 Pro(cheetah0)
OS version:14
App version：4.2.6(267)
Service：FreshRSS

Answer 11 · 2024-07-07T23:59:22.000Z

Unfortunately version 4.2.5.1 crashed again after a while. So I installed 4.2.6 and the app also crashed. I de-installed the app and installed v4.2.6 again and restored my configuration. The logfile size was already 15 MBytes after using FeedMe for over 3 years on this device. I briefly checked the latest entries, it looks as the app isn't able to write to the log when it crashes.
For now it looks good.

Will check if error log is the reason since itbis large.

Answer 12 · 2024-07-08T00:00:12.000Z

@juanico10 reproduzca el fallo y vaya a feedme - configuración - acerca de - comentarios, feedme adjuntará el registro de errores.

Hello,

I attach several reproductions of the application crash.:

error.log
error (2).log

Best regards.

Device:google Pixel 7 Pro(cheetah0)
OS version:14
App version：4.2.6(267)
Service：FreshRSS

Not find related log. 🤔

Answer 13 · 2024-07-08T00:04:41.000Z

@juanico10 reproduzca el fallo y vaya a feedme - configuración - acerca de - comentarios, feedme adjuntará el registro de errores.

Hello,

I attach several reproductions of the application crash.:

error.log
error (2).log

Best regards.

Device:google Pixel 7 Pro(cheetah0)
OS version:14
App version：4.2.6(267)
Service：FreshRSS

Not find related log. 🤔

Hello, you click on the files, I can download them there. If not, I'll send them to you elsewhere.

Best regards.

Answer 14 · 2024-07-08T10:11:27.000Z

Unfortunately version 4.2.5.1 crashed again after a while. So I installed 4.2.6 and the app also crashed. I de-installed the app and installed v4.2.6 again and restored my configuration. The logfile size was already 15 MBytes after using FeedMe for over 3 years on this device. I briefly checked the latest entries, it looks as the app isn't able to write to the log when it crashes. For now it looks good.

I also see "Font request failed, reason：1" in the log file on my device. But those are there already from the beginning.
But I see a similar message as reported by juanico10 on my device. Though I am not sure if this was written to the log at the time of the crash. Also, I searched to the full log and could find this error message "Expected BEGIN_OBJECT but was STRING" every now and then in the past.

`
[2024-07-07 11:44:50][JSON_PARSE]
[2024-07-07 11:44:50]com.seazon.feedme.exception.SyncInterruptException: [JSON_PARSE]
at com.seazon.feedme.task.sync.unit.d.d(Unknown Source:163)
at com.seazon.feedme.task.sync.unit.j.c(Unknown Source:22)
at com.seazon.feedme.task.sync.e.run(Unknown Source:300)
at com.seazon.feedme.sync.work.SyncWorker.doWork(Unknown Source:155)
at androidx.work.Worker$1.run(Unknown Source:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by: com.google.gson.JsonSyntaxException: parse error, json:

503 Service Unavailable

No server is available to handle this request.

at com.seazon.feedme.rss.bo.Entity.wrapException(Unknown Source:40)
at com.seazon.feedme.rss.gr.bo.GrTags$Companion.parseForFreshRss(Unknown Source:119)
at com.seazon.feedme.rss.freshrss.FreshRssApi.getTags(Unknown Source:8)
at com.seazon.feedme.task.sync.unit.d.d(Unknown Source:37)
... 7 more

Caused by: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
at com.google.gson.internal.bind.k$b.e(Unknown Source:72)
at com.google.gson.e.l(Unknown Source:16)
at com.google.gson.e.n(Unknown Source:4)
at com.google.gson.e.q(Unknown Source:9)
at com.google.gson.e.r(Unknown Source:4)
at com.seazon.feedme.rss.gr.bo.GrTags$Companion.parseForFreshRss(Unknown Source:7)
... 9 more
Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
at com.google.gson.stream.a.b(Unknown Source:49)
at com.google.gson.internal.bind.k$b.e(Unknown Source:17)
... 14 more
`

Answer 15 · 2024-07-08T10:17:29.000Z

@juanico10 I mean I download the error logs and check the text, but not find the related error in logs.

Answer 16 · 2024-07-08T10:19:38.000Z

@juanico10 I mean I download the error logs and check the text, but not find the related error in logs.

Hello, it may be because when it crashes it closes unexpectedly.

Answer 17 · 2024-07-08T10:20:53.000Z

Unfortunately version 4.2.5.1 crashed again after a while. So I installed 4.2.6 and the app also crashed. I de-installed the app and installed v4.2.6 again and restored my configuration. The logfile size was already 15 MBytes after using FeedMe for over 3 years on this device. I briefly checked the latest entries, it looks as the app isn't able to write to the log when it crashes. For now it looks good.

I also see "Font request failed, reason：1" in the log file on my device. But those are there already from the beginning.
But I see a similar message as reported by juanico10 on my device. Though I am not sure if this was written to the log at the time of the crash. Also, I searched to the full log and could find this error message "Expected BEGIN_OBJECT but was STRING" every now and then in the past.

`
[2024-07-07 11:44:50][JSON_PARSE]
[2024-07-07 11:44:50]com.seazon.feedme.exception.SyncInterruptException: [JSON_PARSE]
at com.seazon.feedme.task.sync.unit.d.d(Unknown Source:163)
at com.seazon.feedme.task.sync.unit.j.c(Unknown Source:22)
at com.seazon.feedme.task.sync.e.run(Unknown Source:300)
at com.seazon.feedme.sync.work.SyncWorker.doWork(Unknown Source:155)
at androidx.work.Worker$1.run(Unknown Source:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by: com.google.gson.JsonSyntaxException: parse error, json:
503 Service Unavailable

No server is available to handle this request.

at com.seazon.feedme.rss.bo.Entity.wrapException(Unknown Source:40)
at com.seazon.feedme.rss.gr.bo.GrTags$Companion.parseForFreshRss(Unknown Source:119)
at com.seazon.feedme.rss.freshrss.FreshRssApi.getTags(Unknown Source:8)
at com.seazon.feedme.task.sync.unit.d.d(Unknown Source:37)
... 7 more
Caused by: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
at com.google.gson.internal.bind.k$b.e(Unknown Source:72)
at com.google.gson.e.l(Unknown Source:16)
at com.google.gson.e.n(Unknown Source:4)
at com.google.gson.e.q(Unknown Source:9)
at com.google.gson.e.r(Unknown Source:4)
at com.seazon.feedme.rss.gr.bo.GrTags$Companion.parseForFreshRss(Unknown Source:7)
... 9 more
Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
at com.google.gson.stream.a.b(Unknown Source:49)
at com.google.gson.internal.bind.k$b.e(Unknown Source:17)
... 14 more
`

This is rss service api related error. feedme expect a Jason format string, but the response is not a Jason string.

So this is not a related log for this issue.

Answer 18 · 2024-07-08T12:15:19.000Z

@juanico10 I mean I download the error logs and check the text, but not find the related error in logs.

Hello, it may be because when it crashes it closes unexpectedly.

For some reason, there's no crash log when the issue happened. In the attached video, FeedMe app stopped responding a few times from 7:42 PM to 7:45 PM (my local time as seen in the video), but there's no related error in the log within the same time window.
Attached: error.log & screen recording showing app not responding.

bandicam.2024-07-08.19-41-26-182-q28.mp4

Additional info:

After the issue occured, if the same article is opened again (after restarting FeedMe app), the issue doesn't happen anymore.
You can safely ignore all the errors related to java.net.SocketTimeoutException: failed to connect to www.myselfhostedfreshrss.org/xxx.xxx.xxx.xxx (port 24380) from /xxx.xxx.xxx.xxx (port 39756) after 15000ms because sometimes the IP address of my self-hosted FreshRSS server changed, and it took a while for DNS propagation to reach my phone.
I use an app (Greenify) to put other apps to sleep, so sometimes FeedMe app was unable to start with error Unable to start activity ComponentInfo{com.seazon.feedme/com.seazon.feedme.ui.MainActivity}. It would be good if you can take a look at this, but this is probably not relevant here.

Device:Redmi Redmi Note 9 Pro(joyeuse3)
OS version:12
App version：4.2.6(267)
Service：FreshRSS

Answer 19 · 2024-07-08T13:22:49.000Z

@juanico10 I mean I download the error logs and check the text, but not find the related error in logs.

Hello, it may be because when it crashes it closes unexpectedly.

maybe

Answer 20 · 2024-07-12T06:16:36.000Z

@juanico10 I mean I download the error logs and check the text, but not find the related error in logs.

Hello, it may be because when it crashes it closes unexpectedly.

maybe

Hello,

I believe that the 4.2.8 update has solved the error I was having.
This morning I was able to read news without the application closing unexpectedly.
Throughout the day I will test it and report back to you.

Best regards, Juan.

Answer 21 · 2024-07-12T18:52:42.000Z

Today I installed v4.2.8 and after reading a few articles it crashed

Answer 22 · 2024-07-21T02:24:35.000Z

After updating to v4.2.8 6 days ago, I didn't encounter "FeedMe isn't responding" issue anymore. There's also no more error Unable to start activity... when launching app.

Device:Redmi Redmi Note 9 Pro(joyeuse3)
OS version:12
App version：4.2.8(269)
Service：FreshRSS
error.log

Answer 23 · 2024-07-21T08:22:58.000Z

Hi,

I can confirm that the issue didn't re-occured again after installing v4.2.8. It only happened once after I installed this version. Anyways it seems that it only happened on my Tablet but not on the smartphone.

Thanks for the support!

Answer 24 · 2024-07-25T13:16:11.000Z

@juanico10 I mean I download the error logs and check the text, but not find the related error in logs.

Hello, it may be because when it crashes it closes unexpectedly.

maybe

Hello,

I believe that the 4.2.8 update has solved the error I was having.
This morning I was able to read news without the application closing unexpectedly.
Throughout the day I will test it and report back to you.

Best regards, Juan.

Hi!
I can confirm that the problem did not occur again after installing v4.2.8.
Thanks for the support!🎉