I got an issue recently that login Dropbox account within webview2, after type username and passward then hit next, the message will show up on the top said "Your browser appears to be blocking dropboxcaptcha.com, which is required for authentication.". Any help will be appreciated.
WebView Version:
SDK: 1.0.902.49
Runtime: 92.0.902.55
Framework: WPF
OS: Win10
please check in browser site and pop up options and enable. This worked for me in brave browser.
Related
Currently we are automating a website which is showing windows authentication popup before launching the home page by selenium scripts . We tried to add the credential details as part of the URL. but we are not able to bye-pass the credential window . We are able to bye-pass it in Chrome/Firefox browser . But it is not working in DESKTOP safari . could you please help to fix the issue
This is not possible. It is a known issue with Safari and Edge drivers, and is not supported behavior.
https://github.com/w3c/webdriver/issues/385
https://github.com/SeleniumHQ/selenium/issues/5610
https://sqa.stackexchange.com/questions/29598/how-to-bypass-basic-authentication-in-safari-10-with-selenium
I created a Vaadin (8.2.0) web app in Netbeans and uploaded it on a Glassfish (4.1) server. I can access the app's home page in Edge and Firefox, however in Chrome I get this message:
Cookies disabled
This application requires cookies to function. Please
enable cookies in your browser and click here or press ESC to try
again.
I double checked my chrome settings and know that cookies are allowed. I even added the server specifically in the allowed list.
What do think is missing?
As Artur Signell mentioned in the comments, the solution was to simply clear all the cached cookies in the Chrome web browser. After that, the app just worked fine and I didn't get that error.
I was having the same problem. I noticed that switching to HTTPS lead to these errors not occurring. The same site would throw this error when I accessed it via HTTP, but if I went to the site via HTTPS, then the problem did not occur.
In the app I am using Google+ SignIn using oauth2. To authorize user, I am using gapi.auth.authorize(authParams) with javascript flow.
On g+ button click I am calling
gapi.auth.authorize({client_id:xyz, scope:'profile email', authuser:'', prompt:'select_account'})
NOTE:I am doing authuser:'', so that it will ask which account I want to getIn, instead of taking default account.
In browsers like chrome, safari, desktop IE and in devices like android, iphone it is working fine. But in windows phone and in IE Metro browser, on click its opening google's accountChooser page. On selecting the account, in callback I am getting error as on debug.
Unhandled exception at line 13, column 32 in https://ssl.gstatic.com/accounts/o/3655170095-postmessagerelay.js 0x80070005 - JavaScript runtime error: Access is denied.
Couldn't get what is the issue? And how this can be handled?
I asked a question earlier about if it was possible to use Firebase in a Windows 8/WinJS app. #MichaelLehenbauer told me that I just needed to add the following line to my code in order to fix a bug in firebase.js:
Firebase.INTERNAL.forceWebSockets()
This worked great and allowed me to read and write to my Firebase. However, now I am trying to get auth working in Windows 8 and running into many issues. I am trying to use the Facebook login but when I call auth.login("facebook"), my app loses focus and a new tab in the modern Internet Explorer app (not the desktop app) is opened with the typical Facebook login prompt. If I put in my credentials and hit login, nothing happens. I need to go back to my app but then it fires up a new IE tab and the process starts again. Instead of opening a new IE tab, Firebase should internally be opening an in-app dialog like seen in the top image here.
So, since I couldn't get the Firebase Facebook login working in WinJS, I tried doing the Facebook login myself and then create Firebase users using the email/password auth. However, when I run:
auth.login("password", {
email: "me#example.com",
password: "password"
});
I get the following warning (which is the same warning I received from firebase.js befoore Michael suggested to me to force web sockets):
APPHOST9601: Can’t load <https://auth.firebase.com/auth/firebase?&firebase=[my_firebase]&transport=jsonp&email=me%40example.com&password=password&callback=FirebaseSimpleLogin._callbacks._firebaseXDR13889674277557>. An app can’t load remote web content in the local context.
I'm not sure if this is another web sockets issue or not, but it looks like FirebaseSimpleLogin is just not working very well in Windows 8 apps. Are there any workarounds to these problems? Even better, is there any plan to provide full support out of the box with Windows 8?
Windows 8 is now supported out of the box with Firebase Simple Login.
We are developing a web application in asp.net and HTML5 (+ offline feature) and we are using “Add to desktop” button to create the desktop application.
Before access main screen, we have a windows authentication screen, so people can connect using their domain credentials.
In safari, we have almost no problem. It's the expected behavior when we are online. For the offline mode, safari needs to keep an active tab with the website loaded to allow offline access to it, otherwise safari does not find website – even if it’s cached with cache manifest...
In the desktop application (using “Add to desktop” button), the authentication popup on the main page does not appears. When I trace the HTTP requests, I can see 2 requests with a return status of 401. When I look into the logs, safari sandbox throw an exception (twice tries then abort operation)... The screen remains blank.
any ideas anyone or any fix is planned to correct this problem ?
Thanks in advance for any advices.
It's a problem with iOS 7. Windows Authentication only works in "Private Mode" or in another browser such as Chrome or Puffin. However, there isn't a workaround currently available to save an app to the home screen. Here's a thread on the Apple forums about this same issue:
https://discussions.apple.com/thread/5327078?start=60&tstart=0
The new iOS 7.03 fixes this issue.