Closed 0n4t3 closed 10 months ago
Thank you for the report. This is probably related to https://developer.android.com/about/versions/14/behavior-changes-14#runtime-receivers-exported so I guess that we need to set the RECEIVER_EXPORTED
flag. Weirdly enough I'm already on Android 14 (Pixel 7) without any issues.
@0n4t3 You don't happen to have the Logcat Logs for the crash?
@David-Development Grabbed a copy of them, hope this helps
@0n4t3 Thank you for the logs! After reading through the logs.. you are using the legacy login in the nextcloud news app, correct? Could you try to setup the news app again using SingleSignOn? I'm wondering if it's related to the legacy login since the crash message suggests that the Memorizing Trust Manager has some issues validating the certificate. If you use the SingleSignOn Feature the Nextcloud Files App will handle the Certificate Validation.
How to: Just click on your Profile Icon (top right corner) and click on "Login using Nextcloud Files App".
@David-Development yeah I've been using the sign in directly option when getting the error.
I updated the the latest News version, setup the files app, and signed into news using the files app without any issues. I'm not sure how many situations would be effected (sounds like it's isolated to self signed certs?) but it's working without issues after signing in that way.
Thanks!
Closing since the Manual Login is deprecated and it still works with Valid SSL certificates (on Android 14). For self signed certificates the SSO (Login via Files App) option should be used.
After upgrading from 0.9.9.81 to 0.9.9.82 (installed via F-Droid) the content of my feeds disappeared within the app (but still were there in the web interface). After clearing app data and trying to log back I I got the following error:
Downgrading back to 0.9.9.81 fixed the issue and it seems to be working fine as always.
I'm using a Pixel 5a running GrapheneOS, and the Nextcloud is installed as a snap and using a self signed cert.