Stuck on Offline page upon start about dev-android HOT 23 CLOSED

Thanks for those infos @samfcmc . I've verified that this is indeed caused by Service Worker; It is being too aggressive with offline page. I will be deploying a tweak via the web app.

from dev-android.

It seems like the fix was rolled out yesterday by the Chromium team and it will take a few days for everybody to receive it. If you are still hitting the offline page upon start, clearing the cache once or twice should resolve the it as per Chromium team's suggestion.

I am keeping an eye on it if to see if there's any further action we need to take.

from dev-android.

This issue is reproducible by following these steps:

1. Open the app.
2. Turn off wifi / data
3. Open the app again

You will see the error screen.

A workaround to get over it:

1. Go to Settings
2. Clear Data of DEV.to app
3. Open App

Willing to take a look on this and check viable fix if no one will claim the ticket. Seems to be critical.

@maestromac

from dev-android.

@joshuadeguzman I don't need to turn off WiFi or data. After I closed it, it becomes unusable. I am closing it by touching the "Overview" on the bottom side of my phone and force the app to close. Then, I have to delete the app data to be able to use it again.

from dev-android.

I'm aware. I saw Mac land a Service Worker update in master (forem/forem@0af2a0a) which was why I said what I did.

from dev-android.

Judging by the bug's sudden appearance and how it's also affecting Facebook's browser & DuckDuckGo browser, I believe this is a chromium bug https://bugs.chromium.org/p/chromium/issues/detail?id=977784

Additional refs:
https://stackoverflow.com/questions/56681774/update-service-worker-in-facebook-browser
https://stackoverflow.com/questions/56719340/fetch-request-immediately-failing-in-service-worker-running-through-android-we
The patch:
https://chromium-review.googlesource.com/c/chromium/src/+/1675358

from dev-android.

Haven't faced the issue in a while… is still a thing?

from dev-android.

Thanks for the error report @samfcmc . Can you try uninstalling and reinstalling the app? Let me know if the error still persist.

from dev-android.

Describe the bug
I have the same bug as @samfcmc

To Reproduce
Unsure, seems to have started on its own?

Expected behavior
Show the dev.to feed

Smartphone (please complete the following information):

Device: Samsung Galaxy Note 9
OS: Android
Version 9.0.0

Additional context
dev.to app version: 1.2
dev.to Beta: No

First attempt at resolving
Force closed dev.to app
Cleared dev.to app cache
Opened dev.to app
Results: offline screen persisted

Second attempt at resolving
Force closed dev.to app
Cleared dev.to app cache
Cleared dev.to app data
Opened dev.to app
Initial results: feed was shown
Closed dev.to app
Opened dev.to app
Final results: offline screen returned

Third attempt at resolving
Uninstall dev.to app
Install dev.to app
Opened dev.to app
Initial results: feed was shown
Closed dev.to app
Opened dev.to app
Final results: offline screen returned

from dev-android.

I reinstalled the app. I was able to login and see the feed. Later on, when I try to open the app again, the offline screen returns. I can only see the feed the first time I use it after installing the app.

from dev-android.

I'm experiencing this issue too now. I'm going out of the limb to say that this is most likely caused by Service Worker.

from dev-android.

Same here. OnePlus 3t.

from dev-android.

Exact same behaviour as @samfcmc, had to clear data to regain functionality. Appears the fix didn't work?

from dev-android.

The fix to this has to be achieved in the web team. For android the things we can achieve require to know the explicit URL or check on every launch for a reload of the webview.

Doing the reload of the webview will lead to more issues than the fix from the webworker

from dev-android.

Yep the fix will have to be done on the web app. I'm channeling the conversation to here for the time being since I see higher occurrence through the mobile app.

At the moment, I can't seem to reproduce the error at all on my OnePlus 6T Android 9.0.14. Perhaps using both WebViewClient and WebChromeClient is causing some conflict with SW? Whatever it is, it is causing fetch to fail immediately despite having a connection. The most drastic solution that might need to happen is to turn off Service Worker for mobile.

from dev-android.

Clearing cache seems to have resolved the problem on my end. Will be on the lookout for Chrome updates on my devices.

from dev-android.

I cleaned the cache and reinstalled the app. It opened fine. I did not log in and the 2nd time around it was offline again.
Android 9 on Moto X4

from dev-android.

Haven't hit this again in the past week

from dev-android.

Are you still experiencing this issue @neex-io ?

from dev-android.

And right on cue, stuck on offline page again 🤐

Edit: Force stop fixed it for some reason...

from dev-android.

Can confirm the issue hasn't showed up since my last comment.

from dev-android.

Thank you for the update.

This issue is resolved

from dev-android.

This is happening today too on desktop brave

from dev-android.