search

seazon / FeedMe

The documents and forum of FeedMe
1.25k stars 28 forks source link

Continuous crash in the application after updating it #718

Closed juanico10 closed 3 months ago

juanico10 commented 4 months ago

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:

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

Screenshots Screenshot_20240703-185031.png

Device info

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

lduesing commented 4 months ago

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.

hilaily commented 4 months ago

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

seazon commented 4 months ago

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

mdino-gh commented 4 months ago

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.

seazon commented 4 months ago

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

juanico10 commented 4 months ago

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?

seazon commented 4 months ago

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

hilaily commented 4 months ago

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.

mdino-gh commented 4 months ago

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.

juanico10 commented 4 months ago

@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

seazon commented 4 months ago

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.

seazon commented 4 months ago

@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. 🤔

juanico10 commented 4 months ago

@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.

Screenshot_20240708-020203.png

Best regards.

mdino-gh commented 4 months ago

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 `

seazon commented 4 months ago

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

juanico10 commented 4 months ago

@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.

seazon commented 4 months ago

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.

vonguyenkhang commented 4 months ago

@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.

https://github.com/seazon/FeedMe/assets/15910168/93d172d7-d832-421a-9155-47dd24f02f00

Additional info:

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

seazon commented 4 months ago

@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

juanico10 commented 4 months ago

@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.

mdino-gh commented 4 months ago

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

vonguyenkhang commented 4 months ago

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

mdino-gh commented 4 months ago

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!

juanico10 commented 4 months ago

@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!🎉