While automating a testcase using Katalon studio version 8.5.1 Katalon recorder is not responding and webpages keeps spinning and finally, timesout ... we are using one-trust cookie sdk in our webpage to show the cookies consent.
please let me know any one come across the same..thanks..appreciated..
webpages keeps spinning and finally, timesout ... the recorder is not responding
Related
Im trying to create an discord auth on my flutter website using oauth2, webview_flutter & webview_flutter_web.
After click connect button it should redirect user to discord login site, but then this error pops out
Error pops out also on other browsers like chrome or edge.
I was trying to run it in different project, but on android this time and it works fine. So the error must be related to the web version.
I read somewhere that it might be related to iFrame, but it wasn't really explained there.
Any ideas what this error might be related to or how to fix it?
this also happens with other websites.
The Capacitor Browser is having issues with web redirects - with different behaviors in iOS and Android. I think this is a very buggy plugin, but maybe I'm missing something...
My Ionic app uses the Capacitor Browser plugin to present a Federation Login page. There is an "authentication URL" returned upon successful SSO login - or if the user is already logged in then there is an immediate "authentication URL" redirect.
Here's what I am seeing...
iOS: for a first time login, the web redirect works and deep links back into my app -- no problem here. However, if SSO is active, then there is an immediate redirect which the Browser ignores. I can see the URL change, and it works if I open it in a separate mobile web browser.
Android: for a first time login, the web redirect is ignored and the user is left stuck in the browser. Again, if I copy the URL to a separate web browser then it deep links back into the app.
Has anyone done this successfully or have any workarounds? I've tried the "Cordova" and "Awesome" InAppBrowser versions of this plugin, and they don't redirect at all (although they have a bit more control over closing the browser, etc.).
I encountered a problem like this on Android lately,
The in app redirection was down on Android 12, users where locked on a white screen where we normally get the token in the url and redirect in app.
In my case it was related to this :
https://developer.android.com/training/app-links/verify-site-associations?authuser=2
The chrome browser was trying to check this file to verify the hash of the app to perform the redirection but it was unavailable due to internal network configuration, so it was locked.
This check seems to append on Android 12 only, and needed a re-install of the app on users devices (cache on in app browser ?).
Hope this can help.
(Ionic 6 Capacitor)
I am struggling to utlise the angular-auth-oidc-client to add OIDC workflows into my Ionic app (android), although I feel the issues are more Capacitor so not sure that the library is the issue. There are numerous (old) posts on Google of people who have had similar problems, so I'm trying to ascertain the current state of play. I can:
By utilising a custom android scheme in my AndroidManifest, and an 'appUrlOpen' listener in app.component my OIDC login page loads in the Chrome browser on the device, and then returns to the Ionic app and opens the correct app page. Unfortunately because I've opened the login in Chrome it hangs around in the background with the username and password populated. I've no handle to it to close it, and the Capacitor plugins don't help me here.
Alternatively, I can add my ID Provider domain into 'AllowNavigation' in capacitor.config.json. This opens my login page in the app's webview, begins the redirect on successful login but fails (hangs) because Capacitor is not loaded when it attempts Window.Capacitor.triggerevent calls.
This is probably classed as a poor question, and I appreciate that it is light on code, but I'm interested in whether anyone has actually managed to do this successfully, as there are so many dead ends on google and github of people who've given up!
Yes it is possible to complete an Open ID Flow on ionic with capacitor.
You need a capacitor plugin to do so, ionic provides an own payed plugin (https://ionic.io/docs/auth-connect), other alternatives exist.
angular-auth-oidc-client out of the box works only on browser, not on iOS or Android. It seems that some adoption can be made, see https://github.com/damienbod/angular-auth-oidc-client/issues/807.
I am developing a deezer web application (javascript SDK).
I have a simple "hello world" player (example from the deezer dev website); if I start playing a song I can listen just to the 30 secs preview and it is correct, I am not connected to deezer.
What I want to avoid is the automatic deezer connection popup window which appears just after the music start playing. What I would like to do is instead explaining to the user why she has the 30 sec limit and invite her to connect her deezer account. That automatic popup is very very confusing for the average user. Is there a way to prevent it?
Furthermore: it is still not clear to me WHEN this popup is showed: if I am logged in facebook (not in deezer, just in facebook), the popup is showed, otherwise is not.
In order to do a test, I have DELETED my deezer account (which I registered through facebook) but it seems that when I am logged into facebook the Deezer SDK still remember me and launches the popup...
Does anyone has more information about?
There is no way to block that popup. It shows up every time a user needs to register/sign up to stream full tracks (usually after getting the 30 seconds previews). Credentials are cached so if the user is logged in Deezer from another browser window or previous navigation (on Deezer.com or any website using Deezer connect), it won't show up and those credentials will be used.
The only way you can be more proactive about the Deezer registration is to guide your user to your own login button (using DZ.login from the SDK) on your page before getting the popup.
I have a web app, which runs locally, to interface with Facebook. That is, my app would write to the current user's Facebook wall. It worked for me using Firefox 3.6 and Chrome 10, but I have one test user who said it didn't work for him, and he didn't even get to the [Allow] and [Not Allow] screen, and yes, he was using Firefox as well. What could prevent Facebook from processing the request from an identical app (same code)?
and would anyone want to give it a try?
Are you using popups to show the "[Allow] [Not allow] screen"? May be your test user "just" forget to enable the popups on facebook domain. The problem is, my clients experience that, 90% of visitors not allow popups, so the auth process just stops, and no error message has been generated.