https://bugs.kde.org/show_bug.cgi?id=478033
--- Comment #9 from Antonio Rojas <aro...@archlinux.org> --- (In reply to Carl Schwan from comment #8) > So with https://invent.kde.org/pim/kdepim-runtime/-/merge_requests/148 and > https://invent.kde.org/pim/kdepim-runtime/-/merge_requests/149 the situation > looks quite a bit better here. Testing and code review welcome With these I can't even authenticate once. org.kde.pim.ews.client: Failed to retrieve authentication data org.kde.pim.ews.client: Failed to retrieve authentication data org.kde.pim.ews: Authentication failed: Access token request failed org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews: requestAuthFailed - going offline org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews: requestAuthFailed - going offline Please register the custom scheme 'urn' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. org.kde.pim.ews.client: Starting OAuth2 authentication org.kde.pim.ews.client: Launching browser for authentication org.kde.pim.ews.client: PKeyAuth certificates not found org.kde.pim.ews.client: Authentication succeeded Please register the custom scheme 'urn' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. org.kde.pim.ews: Authentication failed: Access token request failed -- You are receiving this mail because: You are watching all bug changes.
