Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

Open from JATOS not working anymore (Opensesame: 4.0.24, OSWeb: 2.2.1, Jatos: 3.9.6)

edited July 17 in OSWeb

Hi all,

Not sure whether to post here or on the JATOS forum.

We're trying out the JATOS 3.9.6 version (from 3.9.5).

For our 3.9.5 version the OSWeb "Open from JATOS" functionality works fine for our self-hosted server.

For our 3.9.6 server it throws an error:

Server does not appear to be a JATOS server:

Expecting value: line 1 column 1 (char 0)

First I figured maybe something was not set up properly with the API keys on the test server, but if I run the curl API test command it comes back without issue.

{"apiVersion":"1.0.1","data":{"id":11,"name":"test","creationDate":1752744609000,"expires":2592000,"active":true,"isExpired":false,"expirationDate":1755336609000,"isAdminToken":true}}   

Using curl to get export a specific study also works fine.

EDIT: I also just tried it on the cortex server, and getting the same error. Again, running curls (e.g. from the Swagger UI page) seem to work fine, and will give me the overview of all available studies.

Any idea what may be going wrong?

Thanks!

Kerwin

Comments

  • Ok, I figured it out, and luckily it has little to do with either..

    I was testing the two servers on two different browsers, and apparently Edge appends a slash to a copied URL, even if you explicitly do not select it..

    Firefox instead behaves as expected. And with a slash at the end of the server URL, it does not work in Opensesame.

    So for anyone else running into the same issue: make sure to remove any trailing slash.

    And perhaps in a future update Opensesame could even trim trailing slashes from the URL?

Sign In or Register to comment.