Project

General

Profile

Actions
Copy link

Bug #692

closed

Fix a crash when the HTTP authentication dialog is displayed when the app is restarted

Added by Soren Stoutner about 4 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Next Release
Assignee:
Soren Stoutner
Start date:
04/17/2021
Due date:
% Done:

0%

Estimated time:

Description

This will require restoring the connection to the handler that is saved in the NestedScrollWebView.

Actions
Copy link
 #1

Updated by Soren Stoutner about 4 years ago

  • Tracker changed from Feature to Bug
Actions
Copy link
 #2

Updated by Soren Stoutner almost 4 years ago

  • Priority changed from 3.x to Next Release
Actions
Copy link
 #3

Updated by Soren Stoutner about 3 years ago

It appears that the app no longer crashes, but it does wait for a long time (perhaps about a minute) before displaying the dialog if a new website uses HTTP authentication after a restart when a prior dialog is open. The restart also clears the previous dialog from the screen.

Actions
Copy link
 #4

Updated by Soren Stoutner almost 2 years ago

  • Status changed from New to Closed

This appears to be WebView behavior that I don't have access to modify. Basically, when the HTTP authentication dialog is dismissed without valid credentials, WebView waits for a timeout before displaying it again.

Actions
Copy link
 #5

Updated by Soren Stoutner almost 2 years ago

Actually, it turns out that I can cancel the handler when the app is restarted. The result is that the webpage visible before the authentication dialog was displayed is loaded on restart, but navigating to the URL that triggers the HTTP authentication dialog will immediately cause it to display, removing the annoying timeout problem.

Fixed in commit: https://gitweb.stoutner.com/?p=PrivacyBrowserAndroid.git;a=commitdiff;h=4395165965c4a211f7c03583ebca6edaa5bf19fe.

Actions
Copy link

Also available in: Atom PDF