Synchronizing to Pavlovia: 'Fingerprint has already been taken'

I followed these instructions and I can now commit and sync with pavlovia. This is excited; however, another issue has arisen… When I run the experiment I can click the “ok” button to actually begin the first routine. It is shaded and unclickable, even after filling out the form. I have tried using safari, chrome and firefox.

This is the url:
https://pavlovia.org/run/jvcasillas/test/html/

EDIT
To be clear, I was referring to these instructions:

git init
git remote add origin [git@gitlab.pavlovia.org](mailto:git@gitlab.pavlovia.org):username/test.git
git add .
git commit -m “Initial commit”
git push -u origin master`

I tried out your test and was able to click the ok button. Instead of “test” I put “00” as the participant ID this may occur because the variable participant can only hold numbers. Another error arose after I got through the first screen which may be due to the experiment being written in python instead of JS. I am having a similar issue with my current experiment.

Yes, the ok button is working for me now too, but only after I added an image to the experiment. But, as you mentioned, after clicking ok the experiment fails with the following message:

Unfortunately we encountered an error:

* when setting the image of ImageStim: image
* when getting the value of resource: ./img/test.jpeg
* **unknown resource**

Try to run the experiment again. If the error persists, contact the experimenter.

It runs fine in builder, but fails in the browser. I’m going to play with it some more now and see if I can get it to work.

UPDATE: It was a silly error regarding the path to the image file. It is working for me now.

Try changing your filename to be img/test.jpeg (without the ./) I’m not sure what ./ will do in a url relative path, and it isn’t needed in the python path either (./ is sort of a bash shell thing). You’ll need to change it in both your conditions file and in the resources/ folder

I’m going to lock this thread because the original error is solved and we’re getting lots of posts about other things. Please create new topics for new discussions.