Chrome UDF

[Iraj]

@Jos

I have done everything from start of the thread till the end. The chrome_example script is working for http sites & for https sites, the automation doesn't happen at all.

[Jos]

No idea what that last statement means as it states both that it works and doesn't work. 
All exact details please.

[Iraj]

@Jos

Chrome Automation is happening on sites where http is enabled. The sites where https is enabled, automation doesn't happen. It only loads the page & doesn't do anything.

[Jos]

great ... so what is it you expect from us now? 

[Iraj]

4 minutes ago, Jos said:

great ... so what is it you expect from us now? 

I was concerned whether the chrome udf works with all sites or only if http sites. Thanks

[Jos]

When is it going to be clear with you that we need the details about the website and the script you have,  as I have now told you ample times?

[Iraj]

52 minutes ago, Jos said:

When is it going to be clear with you that we need the details about the website and the script you have,  as I have now told you ample times?

#Include <Array.au3>
#Include <Chrome.au3>

_ChromeShutdown()
_ChromeStartup("https://auth.pleaseignore.com/login/?next=/profile/")
_ChromeDocWaitForExistenceByTitle("TEST Auth - Login", 10)
_ChromeObjSetValueByName("username","test")
_ChromeObjSetValueByName("password","test123")
_ChromeInputClickByType("submit")

 

Edited August 25, 2020 by Jos

[Jos]

ok we have a start... but we are still "pulling teeth"....  Do you seriously think this is enough detail? 

so what is the problem exactly? Are you getting errors when you run it? 
It really can't be this hard to properly define the issue you have! 

I give up ... maybe others have more patience. 

Edited August 25, 2020 by Jos

[Iraj]

4 minutes ago, Jos said:

ok we have a start... but we are still "pulling teeth"....  Do you seriously think this is enough detail? 

so what is the problem exactly? Are you getting errors when you run it? 
It really can't be this hard to properly define the issue you have! 

I give up ... maybe others have more patience. 

@Jos

Sorry for all this 🙏

[zeenmakr]

#Include <Array.au3>
#Include <Chrome.au3>

_ChromeShutdown()
_ChromeStartup("https://auth.pleaseignore.com/login/?next=/profile/")
_ChromeDocWaitForExistenceByTitle("TEST Auth - Login", 10)
_ChromeObjSetValueByName("username","test")
_ChromeObjSetValueByName("password","test123")
_ChromeInputClickByType("submit")

@Iraj has the issue been resolved? it works fine on my end. let me know, i might be able to walk you thru it. see attached from my screenshot.  

do provide a copy the debug console log or a screenshot from your SciTE window

Edited September 18, 2020 by zeenmakr

[samibb]

Hi

i have tried to run  this file 

 autoit_chrome_native_messaging_host_install.exe

it gave me black screen

i need help for connect with chrome instead of microsoft explorer .

[zeenmakr]

11 hours ago, samibb said:

i have tried to run  this file 

 autoit_chrome_native_messaging_host_install.exe

it gave me black screen

make sure to read thru first several pages of this thread for updated info on how to install it correctly. once everything is installed, chrome extension would call the exe file -you dont run it manually.

[water]

Or you might have a look at the WebDriver UDF.
In my opinion it is the way to go when it comes to browser automation.

[samibb]

dear seangriffin

i did as you said .

Nothing work except the program close and open chrome.

is there any update

i am using 

windows 8.1 enterprise and windows 10 enterprise

Google Chrome is up to date

Version 86.0.4240.75 (Official Build) (64-bit)

 

 

can you help me.

 

[Zok000]

On 9/10/2013 at 4:12 PM, seangriffin said:

INSTALLATION:

STEP 1: Install the AutoIT extension into Chrome.

Open the following link and download the file named AutoIT for Google Chrome.crx:

https://docs.google.com/file/d/0B_6JmwNIIZ06enotRTVFNVdKOXM/edit?usp=sharing

Note - you may be prompted to login with a Google account as this file is hosted on Google Drive.

In your Chrome browser click on the Chrome menu, then select Tools -> Extensions.  Drag the AutoIT for Google Chrome.crx file that you downloaded above, from Windows Explorer, into this page in Chrome.  You should now see AutoIT for Google Chrome listed in the Extensions page in Chrome.  Ensure that the Enabled checkbox next to AutoIT for Google Chrome is checked.  Also make sure the Allow access to file URLs box is checked (very important to make EXAMPLE 2 work below)!!

 

Hi, First time poster

I'm trying to install the "AutoIT for Google Chrome.crx" file in step 1. (Above)

When I drag and drop this file into chrome extensions I get the error:  "Package is invalid: 'CRX_HEADER_INVALID'."  (Screen shot below)

 

I am using Chrome Version 87.0.4280.66 (Official Build) (64-bit) - (Screen shot below)

Does anyone know how to get past this hurdle?

 

Regards Zok

 

 

[vulcan4d]

Same, CRX_HEADER_INVALID on Step1 during extension import.  Something must have changed with a Chrome update.

[GDL]

same problem : CRX_HEADER_INVALID on Step1 during extension import. Someone can help me? thanks

 

[mutleey]

I had the same error when installing the extension.

[burque505]

You could try following the steps for Chrome 87:

1) Unzip the .crx file for the extension to a directory.

2) From chrome://extensions, select 'Load Unpacked' from the menu near the top.

3) Select the directory you created in Step 1 and click "Select Folder". The extension should install without complaint.

4) I may have installed the messaging host out of sequence, so I had copy the key for the extension and paste it into 'manifest.json' over the existing key. That file, along with the messaging host, is at %appdata%\AutoIt3\Chrome Native Messaging Host\manifest.json

5) Make sure all the permissions are correctly set from the extensions management page.

I'm going through the examples now, and so far everything works.

I'm really an AutoHotkey person, so YMMV with this.

Regards,

burque505

 

 

Edited December 20, 2020 by burque505
Complete rewrite

[samibb]

Dear All

i am using

Windows 10 

 version 88.0.4324.104 64 bit

using remote debugging port 9222

after update the script stop getting session ID