Firefox version 79 with UiPath

Feedback Studio
, , , , ,
22

You got me wrong on this :slight_smile:
I never said that you are not good developer. I just wanted to challenge you to try to overcome the issue instead of doing this:

And using the occasion just pointed what’s the best practices. I apologize. It wasn’t my intention.

1 Like
23

Rolling back worked (outside of an occasional glitch), how is it best practice to rework an entire process flow if an updated plugin will fix the issue.
Unfortunately, it is very difficult to anticipate EVERY possibility (or even practical to do so). I use the Re Framework and use try catch, etc. looking for expected (probable) issues.

24

In my opinion, when we go to production, we must avoid upgrading any of the applications we are using for the automation, or if we must, then we do first outside of production environment so we can prepare corrections as needed first.

1 Like
25

I agree with you. Sometimes things slip through.

26

Good news everyone. I got an update for this issue. It should be fixed in one of the future releases. Our devs are working on it.

1 Like
27

Hi Pablito, are we waiting for a new release of a package, or a new release of uipath studio, or a new release of the firefox extension? Any idea on when such update will be available?
I ask like this, because if we are waiting on an update for Studio, it will be several months before a fix is coming, since we only update robot/studio version 2 times a year.

Best regards Mikkel

28

As the update is questionable I would appreciate an advice. My robot stopped working, I cannot use webrecorder and other fixes have not worked. Rolling back Firefox is not an option for me. So do I make a complete new robot using Chrome?

29

This is what i would do, but what do you mean completely new robot? If you are using full selectors everywhere, then this is another thing to change in the future, if you are doing it right, then you should only need to change your parent activities for the web actions, like open browsers, attach browsers etc… Let us know if you need any more help.

30

Please bare with my low knowledge - so by example in an open browser activity instead of Firefox I should just select Chrome and then everything will work?

31

In a project under my development, that will be correct, but as i said, that will work only if all your activities uses partial selectors… see more here: Full versus Partial Selectors

32

I do use partial selectors but I have many Attach Browser so this would mean that I have to change browser type in all of them? Would changing all Attach Broswer to Chrome make my robot work again?

33

Any news when this error will be solved?

34

From what I can see at the moment it should be fixed with the next release.

35

Came out FF 80.0. has anyone tried whether everything works now or the problem remains as with version 79.0 or the problem is only in uipath?
Thanks

36

I am still having the same errors

37

Thanks

38

Release of what? Can you elaborate on if we can get by with just upgrading a package that the project depends on. In which case what package is responsible for the iFrame issue?

39

From what I see, the fix should be live with the latest 20.10 Community Preview. You will also need to make sure you update your UIAutomation package to the latest version.

Updating the Firefox plugin, if available, should be done too.

40

I did the update but it is still NOT working!

When can we expect an update that will correct the error?

41

We still have updates disabled to avoid this.
To bypass the notifications that updates are available, we used method #2 from this link: