Newsblur is crashing just after login. Submitted report on crash dialog.
I wondered if this behavior had anything to do with the recent Webview issues, so uninstalled its updates but issue remains.
Poco X3 Android 10
I have since installed fixed Webview 89.0.4389.105 but issue with Newsblur remains.
Can you try the beta app? You can enroll in the Play Store.
Yes this was happening with the beta, I tried with stable with same result…
Below the error. I tried to disable custom DNS to same result.
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:399)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:289)
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:919)
Caused by: java.lang.IllegalArgumentException: Expected URL scheme ‘http’ or ‘https’ but no colon was found
at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1260)
at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1633)
at okhttp3.Request$Builder.url(Request.kt:184)
at com.newsblur.network.APIManager.post_single(APIManager.java:767)
at com.newsblur.network.APIManager.post(APIManager.java:744)
at com.newsblur.network.APIManager.post(APIManager.java:779)
at com.newsblur.network.APIManager.login(APIManager.java:108)
at com.newsblur.fragment.LoginProgressFragment$LoginTask.doInBackground(LoginProgressFragment.java:72)
at com.newsblur.fragment.LoginProgressFragment$LoginTask.doInBackground(LoginProgressFragment.java:63)
at android.os.AsyncTask$3.call(AsyncTask.java:378)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
… 4 more
Thanks for posting the crash report! I added a ticket and it’ll hopefully get fixed before the upcoming Android release.
@Roberto_Santana Did the crash first started to happen around the time you reported it or was it on your first interaction with NewsBlur from that phone? Thanks
It was working fine before up until I reported this.
With the Fdroid version I get a slightly different error:
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:399)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:289)
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:919)
Caused by: java.lang.IllegalArgumentException: unexpected url: robsan/api/login
at okhttp3.Request$Builder.url(Request.java:143)
at com.newsblur.network.APIManager.post_single(APIManager.java:690)
at com.newsblur.network.APIManager.post(APIManager.java:667)
at com.newsblur.network.APIManager.post(APIManager.java:702)
at com.newsblur.network.APIManager.login(APIManager.java:104)
at com.newsblur.fragment.LoginProgressFragment$LoginTask.doInBackground(LoginProgressFragment.java:81)
at com.newsblur.fragment.LoginProgressFragment$LoginTask.doInBackground(LoginProgressFragment.java:72)
at android.os.AsyncTask$3.call(AsyncTask.java:378)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
… 4 more
I’ve tried to replicate the crash on two devices but with no success so far.
Do you have access to another Android device that you could test login? It would help narrow down the possibilities.
Yes I have an older tablet still on Android 7 and was able to login and use the app there. So it seems the issue is particular to this phone. How can I troubleshoot further?
@Roberto_Santana Since it worked a week ago I assume the issue on your phone is related to WebView.
I’d clear cache (and optionally storage) for WebView and Play Store(it will force it to get the latest app versions), restart the phone and install any updates from Play Store. I’d also explicitly check the WebView system app in Play Store to see if there are new versions available. Concluding with an uninstall and install of NewsBlur.
Let me know if that helps.
I had done so before but repeated the suggested procedure once more: issue remains. I also tried beta, dev, canary Webview with same result. I’m not sure if this is Webview related, as I didn’t have issues with any other apps.
Having been unable to use newsblur on mobile for almost a month now, I have moved on to a competitor (who has a quite nice and modern mobile app BTW). Also had to jump through hoops just to export my saved items - I noticed an older thread on this subject and just cannot believe this functionality is still not available. Thus I will not be renewing my subscription. It was a good 8 years and I wish you all the best.
Sorry it didn’t work out and I still have no idea what caused your crash. If you end up wanting to come back to NewsBlur, I’d be happy to help figure out what’s going on. We also just released a new version a couple days ago, so be sure to try that out.
Yes I did try that new version, still crashes. Can you not create a debug apk to collect further logs? I don’t understand how a paying customer can be left in the dark for almost a month…
Also sadly in your reply you did not address the issue with saved items export.
Saved story export has always been punted because there’s no set standard for how they look. So if I had a JSON file that you could download with all fo your saved stories, what would you do with it? If you do anything, then you’re already able to use the API to download the saved stories (and the NewsBlur API makes it easy to download them), so for the handful of people who have to know-how to do anything with them, they can already download them.
Plus saved stories have RSS feeds, so they are already exportable today.
As for the debug apk, we have a feedback reporting functionality built into the Android app (Manage > Send feedback) and that gives us a whole lot to work with, but if your app is crashing, then you can’t even access it.
By the way, what’s the “robsan” in the URL above? Are you using a custom domain?
Well you could export to a html bookmarks file - this way one could easily import it to a browser. The workarounds some users have developed take this approach and convert the json to html, unfortunately they are not working anymore.
My point is: if it’s easy to subscribe and import opml, the inverse should be easy as well (for the average user), otherwise we have a data lock-in scenario.
robsan is my username (I don’t use a custom domain).