Is there a way to run the chrome browser in the non headless mode in Heroku app.In default the Build packs are in the headless mode. But for my code i want the chrome browser to open so that user can scan the qr code for whats app functionality.Can someone help me..
Related
When I need to make an Android App available in development, I use Play Console to do it, because this tool gives us an option to up the App in DEV to testing, before launching it in Production, that allows any user with link make a download of app by PlayStore to test it.
Is it possible, or exists any tool of Google that allow the same steps above, to deploy a Chrome Extension to testing, before launching it in Production, that can be accessed by any user with link to download and install it on Chrome browser?
P.S. I don't see the option in Chrome Web Store to up an extension to testing like in play console with apps.
The problem I am trying to solve is to login into a site that has SSO. I will need to login with different credentials at times so I don't want to SSO in. Therefore, I will open up an incognito tab in Chrome so the SSO login popup will show up every time: chromeOptions.addArguments("incognito"); This works fine when I am running not in a headless mode and using Java Robot to input the credentials.
However, when I run this in headless mode: chromeOptions.addArguments("headless"); I am back to square one where I got SSO'd in into my personal account without the manual control of inputting in different credentials. That's not what's happening when I have incognito in non-headless mode.
How exactly do I configure my Chromedriver through Java to be BOTH headless and incognito?
I need headless mode because I need to run this inside a Docker container.
I'm new to Cypress and recently started implementing e2e tests for our system. A peculiarity of this system is that the authentication happens on a popup window.
I've already successfully created a simple test that loads the site, waits for the authentication to complete and then asserts that the page title is shown. This test runs without errors using the cypress client (cypress open), but when I run it in headless mode (cypress run --headless) the test fails.
When I see the video from the headless run, I don't see the popup window appear like it does when I run it with the GUI. Has anyone else had an issue like this where popup windows don't show on headless mode?
I also found this bug on the Chromium site related to issues displaying popup windows in headless mode, so it might be related to that, but the bug appears as closed.
I'm using Cypress 6.1.0 and Chrome 87
Thanks in advance for any help.
This was being caused by an issue with the integration of my website with another service that for some reason only occurred on headless mode. After fixing that, it works ok.
I needed to debug a PWA that throws an error only when running in standalone mode, this PWA worked fine on the same device but when opened from Google Chrome directly.
I was debugging this web app by connecting from the desktop's Chrome developer tools with USB debugging enabled, but this was quite slow, as I had to build the PWA and publish it to be able to check the changes that I've made because this error was not thrown in development mode (The app is built using Nuxt.js).
That error was related to a code that checks if the web app is running in standalone mode:
window.matchMedia('(display-mode: standalone)').matches
I have resolved the issue but is there a way to simulate this display-mode: standalone from Google Chrome on the desktop?
we have an C# backend that launches and integrates with a chrome webapp in kiosk mode. we have a message that is executed from webapp that tells the backend to close chrome and show the backend ui (a service ui).
This works fine, but we are using Process.Kill to close chrome. We've got other issues that we believe that may be related to left overs from the harsh closing of chrome.
What is the proper way to close chrome, once Kiosk mode has been entered?