Experiment works on Chrome, doesn't work on Safari: psychoJS.experiment._unfinishedLoops.at is not a function

Online experiments
,
23

Thanks for your quick response. I just checked again and it seems your code does not work on Safari after all. I am using PsychoPy version v2022.2.5. When I click next block, I get the unfinished loops error. When I continue to click through by clicking next trial, it works until I get to the last trial in the block. Then it throws the same error. Any idea why this doesn’t work on that version and how to fix it?

24
25

When I change the version, my entire experiment does not run anymore locally on my machine and I get other errors on Safari. This may be due to me having added a lot of custom code, so this may not be compatible with my task unfortunately and changing all of that is not really an option because the experiment is rather complicated. I’m not really sure what else I can do. I appreciate any other suggestions I could try.

26

I’ve just upgraded loop-test [PsychoPy] to the pre-release version of 2024.1. Please could you test it again and if it gives an error on Next Block please give the details of your operating system and browser?

I’ve added a note to the text with the PsychoPy version so if you don’t see 2024.1.0rc7 then please try an incognito browser.

27

Thanks for looking into this more. I tried to run it on Safari (regular and incognito) but the same error persists. I have a MacBook Pro M1 using macOS Monterey Version 12.1 and am running this on Safari Version 15.2.

28

Hi, any one else have observations about this issue? I’ve been getting emails from Safari-based participants who are experiencing this error for a study programmed in v2023.2.3. I’m a little surprised because I tested the full study in Safari once and it worked fine (I’ll have to check on that version of Safari and the hardware for the computer, which I borrowed), but perhaps the error also depends on the specific version of Safari or hardware configuration?

29

We’ve decided to deprioritise trying to fix this, because we can’t get enough data about which (if any) devices still have a problem with breaking out of loops in the latest release.

30

Hi, just encountered this issue too and I think I know the reason.

The reason for this bug is that the browser the participant is using doesn’t take .at() method (read here: Array.prototype.at() - JavaScript | MDN).

The solution is to ask your participants to update their browsers to 2022 later.

1 Like