power automate desktop not connecting with browser extension - automation

I have installed the latest versions of power automate desktop and browser extension, and I'm using the Microsoft Edge browser, before the latest update come, it worked perfectly, but after the update it not working.
every time I run the flow it shows this error:
"Failed to assume control of Microsoft Edge (Communication with browser failed. Try reloading extension)."

With the new version you also have to make sure developer tools are enabled in your browser.
See the information here about manifest v3
When I updated to the latest version of PAD I also had major issues lucky I was able to roll back to the previous version.
I'm aware this might not solve your issue, but the only way I could get mine working again was to uninstall 2.27 and reinstall 2.26, lucky I had the install for 2.26 as I couldn't find a previous version download link on the MS website anywhere.

Related

ArcGIS initializing or loading error: unable to establish connection to https://www.arcgis.com

I've been having issues opening Arcgis pro for a few days. I've tried all the options provided by the ESRI help team and nothing has worked so far. I have set the TLS 1.2 requirement, the organization and group permissions, added it to trusted sites on my anti virus, etc. I have uninstalled and reinstalled ArcGIS pro and it didn't work. I uninstalled a few programs I though were redundant on my system and suspect that I may have touched once of its dependencies. I uninstalled a version of conda, visual studio, and I suspect a version of python too. This was all in a bid to get arcpy working on this system as the import arcpy command through python IDLE and Pycharm came back with errors. I still have other versions on the system but still can't load Arcgis pro. The help team reached out last 24 hours ago as this error is unusual.
Do you have any ideas on how to get my pro working again please?

Is analytics available with the MobileFirst Platform CLI developer edition?

I have installed the MobileFirst Platform CLI developer edition from https://developer.ibm.com/mobilefirstplatform/install/#clui
I am trying to investigate the analytics of the application, but this doesn't seem to be properly installed from here.
I am able to create a MFP server, start it and access the console. It doesn't have a link to the analytics in the top-right of the console as it does in the developer edition provided by Eclipse. Is this behaviour as expected or is there something missing?
I have tried installing this package twice. I am running on OSX 10.10
In the Liberty servers directory, /Users//.ibm/mobilefirst/6.3.0/server/wlp/usr/servers, I can see the Worklight folder. It has an _analytics.war file in it (which is different from my Eclipse install which has a worklight-analytics.war and worklight-analytics-service.war)
And in the messages.log file, I am getting messages saying that the web application _analytics is available.
But I then a number of messages with
com.worklight.analytics.api.AnalyticsHttpService.sendDataToURL target server response code: 404
Going directly to http://localhost:10080/_analytics responds with an "Authorization failed" message.
Update - Got it working
I uninstalled the dev edition CLI and downloaded the CLI from Passport Advantage and installed it from there. The analytics feature now seems to work. Although the link to it is still not available in the top right of the console.
I don't know if it's a different install package, or an issue on my Mac that I inadvertently resolved, but the analytics feature is now working
The issue here was that the version you originally downloaded was not up-to-date.
This will be corrected soon.
Proper mechanisms will be put in place so that this will not happen again.
Yesterday I downloaded and installed the publically available MobileFirst Platform 6.3 CLI from https://developer.ibm.com/mobilefirstplatform/install/#clui. I created a simple app which connects to the MFP server.
Result: Analytics works without any problem.
So you do not have to buy the product just to use the CLI with analytics.

GitHub asks me to "add a new helper tool" every time I open it

Every time I open GitHub for Mac it asks me to "add a new helper tool" and prompts me for my password. Every time I enter my password (I am an admin on this computer) but I see no noticeable changes afterwards and the prompt comes back every time I reopen GitHub. (See attached photo for the prompt window.)
I am running OSX Yosemite Version 10.10 on a Late 2012 Mac Mini (2.5 GHz Intel Core i5).
Unsure if this is related but I am running GitHub version "Reactive Barbecue (186)". According to the GitHub for Mac release notes this is NOT the newest version, but when I select "Check for updates" it says I have the latest version. Would a fresh install of GitHub solve this? This is more of a nuisance and doesn't noticeably impede my work.
I use GitHub daily for XCode pushes with my coworkers. They all use MacBook Airs and OSX Yosemite but do not have the same issue as me.
I was also having this problem.
Cause? Maybe GitHub.app was confused by multiple git installations: XCode's Command Line Tools and Homebrew's copy (a newer version and includes bash completion).
Running the shell command git credential-osxkeychain returned a "usage" line, so a helper was installed despite that message.
Fix: Downloading and running GitHub Desktop successfully installed its helper. I think GitHub Desktop.app is the new name for GitHub.app, so apparently they fixed the bug by now.
BTW: They wrote "If you're using GitHub for Mac or Windows, the upgrade is automatic.", but their automatic upgrade didn't fix this problem nor switch to "GitHub Desktop.app".
The only solution I found so far was to delete the GitHub for Mac application. Then I re-downloaded the app (the most recent version 193 "Big Feels").
It then gave me a popup saying I needed to uninstall the old version since OSX now comes with Git commands by default (or something like that?). Clicking "Uninstall now" made the app crash so I had to select "Uninstall later". This is sort of only a fix for the symptom since GitHub could keep telling me to uninstall every time I open it, but at least it says I have the most recent version now.
Use AppCleaner and nuke it. Reinstall.

Can I run multiple versions of Google Chrome on the same machine? (Mac or Windows)

This fabulous answer suggests there’s no way to run multiple versions of Google Chrome on one machine.
Every now and then you’ll get a website user stuck on an old version of Chrome (no idea how, but it happens — maybe they installed the standalone version?) with an issue, and you need to be able to verify it. Bit difficult to do that without their browser version around.
Does anyone know if there’s actually a way to do this? I.e.
Obtain an installer for an older version of Google Chrome (Google seems to keep very quiet about versions, which is great for users, less great for developers trying to support old versions)
Run two versions of Google Chrome on one machine
In the comments, I mentioned a step-by-step method to easily install multiple Chrome versions, side-by-side. This answer quotes my original answer, and includes a script which does the job for you.
Quoted from: section 7 of Cross-browser testing: All major browsers on ONE machine:
Chrome: Stand-alone installers can be downloaded from File Hippo. It is also possible to run multiple Chrome versions
side-by-side.
Although Sandboxie can be used, it's
recommended to use the next native method in order to run multiple
versions side-by-side.
Download the desired version(s) from File Hippo.
Create a main directory, e.g. C:\Chrome\.
Extract the installer (=without installing), using 7-Zip for example. After extracting, a chrome.7z archive is
created. Also extract this file, and descend the created Chrome-bin
directory. Now, you see chrome.exe and a dir like 18.0.1025.45.
Move chrome.exe to 18.0.1025.45, then move this directory to
C:\Chrome. The remaining files in Chrome-bin can safely be
deleted.
Create a shortcut for each version:
"C:\Chrome\18.0.1024.45\chrome.exe" --user-data-dir="..\User Data\18" --chrome-version=18.0.1025.45
Explanation of this shortcut:
"C:\Chrome\18.0.1024.45\chrome.exe" • This is the
launcher
--user-data-dir="..\User Data\18" • User profile, relative to the location of chrome.exe. You could also have
used --user-data-dir="C:\Chrome\User Data\18" for the same effect.
Set your preferences for the lowest Chrome version, and duplicate the User profile for each Chrome version. Older Chrome versions
refuse to use User profiles from new versions.
--chrome-version=18.0.1025.45 • Location of binaries:
* The location (eg `18.0.1025.45`) must be the name of the directory:
* Must start and end with a number. A dot may appear in between.
* The numbers do not necessarily have to match the real version number (though it's convenient to use real version numbers...).
Regarding configuration: All preferences can be set at
chrome://settings/. I usually change the home page and "Under the
hood" settings.
Disable auto-updates: http://dev.chromium.org/administrators/turning-off-auto-updates
(the old version of this answer referred to Old Apps for old Chrome versions, but they do not offer direct download links any more through the UI. The files do still exist, I've created a shell script (bash) to ease the creation of a local repository of Chrome versions - see https://gist.github.com/Rob--W/8577499)
##VBScript which automates install, config & launch
I've created a VBScript which installs and configures Chrome (tested in XP and Windows 7). Launch the script, and a file dialog appears (or: Drag & drop the chrome installer on the VBS). Select the destination of the Chrome installer, and the script automatically unpacks the files and duplicates the profile from a pre-configured base directory.
By default:
The Chrome binaries are placed in subfolders of C:\Chrome\.
The User profiles are created in C:\Chrome\User Data\.
The user profiles will be duplicated from the directory as specified in the sFolderChromeUserDataDefault variable, which is C:\Chrome\User Data\2\ by default.
After the first Chrome installation, set your preferences (Home page, bookmarks, ..). Then modify the variable (see 3.) in the source code. After that, installing and configuring Chrome is as easy as pie.
The only dependency is 7-zip, expected to be located at C:\Program Files\7-zip\7z.exe.
I adopted #RobW's nice answer to get it working on Mac OS X 10.8. Other versions of Mac OS X may probably work too.
The little extra work is actually only needed to keep your original Google Chrome user settings and the old version separated.
Download another version of Google Chrome, like the Dev channel and extract the .app file
(optional) Rename it to Google Chrome X.app – if not already different from Google Chrome.app
(Be sure to replace X for all following steps with the actual version of Chrome you just downloaded)
Move Google Chrome X.app to /Applications without overwritting your current Chrome
Open the Terminal, create a shell script and make your script executable:
cd /Applications
touch google-chrome-version-start.sh
chmod +x google-chrome-version-start.sh
nano google-chrome-version-start.sh
Modify the following code according to the version you downloaded and paste it into the script
#!/usr/bin/env bash
/Applications/Google\ Chrome\ X.app/Contents/MacOS/Google\ Chrome\ X --user-data-dir="tmp/Google Chrome/X/" & disown
For example for Dev Channel:
#!/usr/bin/env bash
/Applications/Google\ Chrome\ Dev.app/Contents/MacOS/Google\ Chrome\ Dev --user-data-dir="tmp/Google Chrome Dev/" & disown
(This will store Chrome's data at ~/tmp/Google Chrome/VERSION/. For more explanations see the original answer.)
Now execute the script and be happy!
/Application/google-chrome-version-start.sh
Tested it with Google Chrome 88 on a Mac running OS X 10.15 Catalina
Your mileage may vary (mine sure did), but here's what worked for me (current version of Chrome as of this post is 33.x, and I was interested in 24.x)
Visit the Chromium repo proxy lookup site: http://omahaproxy.appspot.com/
In the little box called "Revision Lookup" type in the version number. This will translate it to a Subversion revision number. Keep that number in mind.
Visit the build repository: http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html
Select the folder corresponding to the OS you're interested in (I have Win x64, but had to use Win,because there was no x64 build corresponding to the version I was looking for).
If you select Win, you could be in for a wait - as some of the pages have a lot of entries. Once the page loads, scroll to the folder containing the revision number you identified in an earlier step. If you don't find one, choose the next one up. This is a bit of trial and error to be honest - I had to back up about 50 revisions until I found a version close to the one I was looking for
Drill into that folder and download (on the Win version) chrome-win32.zip. That's all you need.
Unzip that file and then run chrome.exe
This worked for me and I'm running the latest Chrome alongside version 25, without problems (some profile issues on the older version, but that's neither here nor there). Didn't need to do anything else.
Again, YMMV, but try this solution first since it requires the least amount of tomfoolery.
For those who don't care if it's "Google Chrome", I suggest using "Chromium" instead.
See: Download Chromium
Look in http://googlechromereleases.blogspot.com/search/label/Stable%20updates for the last time "44." was mentioned.
Loop up that version history ("44.0.2403.157") in the Position Lookup
In this case it returns a base position of "330231". This is the commit of where the 44 release was branched, back in May 2015.*
Open the continuous builds archive
Click through on your platform (Linux/Mac/Win)
Paste "330231" into the filter field at the top and wait for all the results to XHR in.
Eventually I get a perfect hit: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/330231/
Sometimes you may have to decrement the commit number until you find one.
Download and run!
Though this seems to be an old question with many answers I'm posting another one, because it provides information about another approaches (looking more convenient than already mentioned), and the question itself remains actual.
First, there is a blogpost Running multiple versions of Google Chrome on Windows. It describes a method which works, but has 2 drawbacks:
you can't run Chrome instances of different versions simultaneously;
from time to time, Chrome changes format of its profile, and as long as
2 versions installed by this method share the same directory with
profiles, this may produce a problem if it's happened to test 2 versions
with incompatible profile formats;
Second method is a preferred one, which I'm currently using. It relies on portable versions of Chrome, which become available for every stable release at the portableapps.com.
The only requirement of this method is that existing Chrome version should not run during installation of a next version. Of course, each version must be installed in a separate directory. This way, after installation, you can run Chromes of different versions in parallel. Of course, there is a drawback in this method as well:
profiles in all versions live separately, so if you need to setup a profile in a specific way, you should do it twice or more times, according to the number of different Chrome versions you have installed.
A small virtual machine maybe?
Try VirtualBox a freeware program to install virtual machines (a lot of work for what you want to do, but it'll work)
I think I might have figured this out on Windows. You can run different versions of Chrome at the same time!
Do the following:
Copy over the version number directory into the usual c:\users\yourUser\appdata\local\google\chrome\application directory (I am assuming you had a backup of the older chrome version directory before the update occurred)
Copy over the chrome.exe from the older version as a new name such as chrome_custom.exe
Run chrome as chrome_custom.exe --chrome-version=olderVersion --user-data-dir=newDir
That's it! I use this method to run automated test on Chrome with Selenium, until selenium catches up and works well with the latest Chrome.
As professional testers, my friends use Spoon.net browsers section to test compatibility of site in various browsers. Hope this should help you.
I have done the following on a Citrix XenDesktop VM, however you could just do this on your local PC:
Microsoft Virtual PC
If you are running Windows 7, you can download Microsoft virtual PC and create as many copies of Virtual PC as you need for testing without any licensing issues:
http://www.microsoft.com/windows/virtual-pc/default.aspx
This requires no additional Windows licenses; you simply set up multiple machines with different browsers on them. You can run the browsers out of the window by following the tutorial available here:
http://ieblog.members.winisp.net/images/InstallingXPMode.htm
Installing Browsers
You will need to create at least 3 virtual PC's (tip: keep the memory down to 256mb for each virtual PC to avoid wasting memory on the virtual desktops).
On the first VPC I installed this:
http://tredosoft.com/Multiple_IE
along with Chrome 1, Safari 3.1, Opera 8.
On the second I installed Internet Explorer 7, Chrome 3, Safari 3.2.1, Opera 9.
On the third I installed Internet Explorer 8, Chrome 8. Safari 4.0.5, Opera 10.
On Windows 7 (native machine) I had Internet Explorer 9, Chrome 11, Safari 5, Opera 11 and for Firefox I install the following app natively too:
http://utilu.com/UtiluMFC/
Personally I would not go back further than 5 years with compatibility (other than IE for government networks) unless you have a specific requirement (I split Chrome & Opera across years as I decided there were just to many releases). However, if you find that someone has a specific issue with a site using a specific version of the browser it becomes very easy to install additional virtual machines to run additional browser versions.
Obtaining Older Browsers
You can download older versions of Chrome from here:
http://www.oldapps.com/google_chrome.php
and Opera here:
http://www.oldapps.com/opera.php
Virtualizing The Test Platform (Optional)
I use Xen Desktop to virtualize the testing platform so that I can use it anywhere and have included my favorite development tools on there as well:
http://deliver.citrix.com/go/citrix/XenDesktop
The express edition is available for free.
A Good Commercial Alternative
Another great product I recently came accross is Stylizer which is a CSS editor that installs multiple versions of browsers for testing purposes, however this is a commercial paid for product but is very good and worth the small fee they require to run it.
I've recently stumbled upon the following solution to this problem:
Source: Multiple versions of Chrome
...this is registry data problem: How to do it then (this is an example for 2.0.172.39 and 3.0.197.11, I'll try it with next versions as they will come, let's assume I've started with Chrome 2):
Install Chrome 2, you'll find it Application Data folder, since I'm from Czech Republic and my name is Bronislav Klučka the path looks like this:
C:\Documents and Settings\Bronislav Klučka\Local Settings\Data aplikací\Google\Chrome
and run Chrome
Open registry and save
[HKEY_CURRENT_USER\Software\Google\Update\Clients\{8A69D345-D564-463c-AFF1-A69D9E530F96}]
[HKEY_CURRENT_USER\Software\Google\Update\ClientState\{8A69D345-D564-463c-AFF1-A69D9E530F96}]
keys, put them into one chrome2.reg file and copy this file next to chrome.exe (ChromeDir\Application)
Rename Chrome folder to something else (e.g. Chrome2)
Install Chrome 3, it will install to Chrome folder again and run Chrome
Save the same keys (there are changes due to different version) and save it to the chrome3.reg file next to chrome.exe file of this new version again
Rename the folder again (e.g. Chrome3)
the result would be that there is no Chrome dir (only Chrome2 and Chrome3)
Go to the Application folder of Chrome2, create chrome.bat file with this content:
#echo off
regedit /S chrome2.reg
START chrome.exe -user-data-dir="C:\Docume~1\Bronis~1\LocalS~1\Dataap~1\Google\Chrome2\User Data"
rem START chrome.exe -user-data-dir="C:\Documents and Settings\Bronislav Klučka\Local Settings\Data aplikací\Google\Chrome2\User Data"
the first line is generic batch command, the second line will update registry with the content of chrome2.reg file, the third lines starts Chrome pointing to passed directory, the 4th line is commented and will not be run.
Notice short name format passed as -user-data-dir parameter (the full path is at the 4th line), the problem is that Chrome using this parameter has a problem with diacritics (Czech characters)
Do 7. again for Chrome 3, update paths and reg file name in bat file for Chrome 3
Try running both bat files, seems to be working, both versions of Chrome are running simultaneously.
Updating:
Running "About" dialog displays correct version, but an error while checking for new one. To correct that do (I'll explain form Chrome2 folder):
1. rename Chrome2 to Chrome
2. Go to Chrome/Application folder
3. run chrome2.reg file
4. run chrome.exe
(works the same for Chrome3)
now the version checking works. There has been no new version of Chrome since I've find this whole solution up. But I assume that update will be downloaded to this folder so all you need to do is to update reg file after update and rename Chrome folder back to Chrome2. I'll update this post after successful Chrome update.
Bronislav Klucka
I have tried the various way to test one of a scenario which was chrome browser specific issue.
Best Solution a/c to me: Use Portable Versions
Step-0: Uninstall your currently installed Google Chrome
Go to Control Panel > Uninstall a program > Click Google Chrome > Uninstall
Step-1: Download the portable chrome version & Rename
Download the portable version of your choice from Portable Older Chrome Versions and save it instead of running it directly.
Go to downloaded file location and Rename the file to end with _online.paf.exe. Example:
Rename from google-chrome-portable-96-0-4664-93.exe to google-chrome-portable-96-0-4664-93_online.paf.exe
Step-2: Install the portable version
Click on the renamed exe file to continue with the installation.
When asked for Destination Folder path -> Rename it to match version (just to avoid conflict with other versions and identify) as shown below.
Step-3: Finally Run the downloaded version:
Go inside the portable installed folder and from there run GoogleChromePortable.exe like below.
Whoa!! This works. Thanks a lot to the creators of Portable Chrome Versions.
Rob W answer works if you can extract chrome.7z from the installer file, Unfortunately, the installer file is not extractable anymore, but you can find chrome.7z file in this address if you have installed chrome and it updated itself:
C:\Program Files (x86)\Google\Chrome\Application\95.0.4638.54\Installer
Or search your hard disk for chrome.7z file to find where Google stores update files for your OS.
After extraction as Rob W mentioned go to extracted folder and run new chrome with command:
.\chrome.exe --user-data-dir=".\User Data" --chrome-version=95.0.4638.54
Oldapps.com has old versions of Chrome available for download, and they’re the standalone versions, so combined with #SamMeiers’ answer, these work a treat.
The Google Chrome support forum has some good discussion of getting old versions of Chrome.

Is the new IE9 a standalone browser

Anyone that has installed the new IE9 know if I can keep IE8 installed? I do a lot of web testing and don't want to update to IE9 if I loose IE8.
best way is to install a Virtual Machine
Per Microsoft:
If you are running Windows Vista or
Windows 7 on your computer, you can
install the Internet Explorer 9 Beta
to replace your existing version of
Internet Explorer. After you install
Internet Explorer 9, you can uninstall
it to restore the previously installed
version of Internet Explorer.
So no, it will overwrite IE8 (at least the Beta will. I suppose this is not guaranteed to be the same for the release version).
I use Virtual PC with images of the browsers I need to test, but also and more lately, IETester, http://www.my-debugbar.com/wiki/IETester/HomePage. It allows you to run multiple versions of IE side by side.
If you want to be able to play with the new features of IE9 without installing the entire browser (which will replace IE8) you can install the Platform Preview. The PP is stand-alone, includes the latest features and bug fixes and has been getting updated roughly every 8 weeks. You can get the latest Platform Preview at:
www.ietestdrive.com
FYI: the production IE 9 does not accurately reproduce IE 8. I've got a CSS issue I'm chasing down now because IE 9's IE 8 mode isn't the same as real IE 8.
If you are concerned with testing how your site looks in IE8/7, you can use the Developer Tools (press F12) to switch the Browser modes and Document modes so that IE9 interacts with the web server as a different user agent, and renders the HTML document according to the version rules.
http://msdn.microsoft.com/en-sg/ie/ff468705(en-us).aspx#_New_Dev_Tools
IE9 beta is released as a Windows update, so after installing it and playing around, you can remove it from Programs and Features -> Installed Updates, which will recover IE8.
hit f12 on ie9, it will pop up the debug console. In the menu there is a browser mode option where you can set the browser to display as ie8 and a bunch of other versions too.
Also, if you're mouse focus is on the console and you hit ctrl+r, it will clear your browser cache... This is a feature that all the other browser debuggers lack.. ability to quickly clear cache.... I'm rambling now.
The best way to see your site on old versions of IE is that:
If you have IE9+, open your current version of InternetExplorer, press F12, click on "Browser Mode" tab, then choose the version you want.
see screenshot here:
Works better than IE-tester, and easier than using virtual machine.