agen judi bola , sportbook, casino, togel, number game, singapore, tangkas, basket, slot, poker, dominoqq, agen bola
. Semua permainan bisa dimainkan hanya dengan 1 ID. minimal deposit 50.000 ,- bonus cashback hingga 10% , diskon togel hingga 66% bisa bermain di android dan IOS kapanpun dan dimana pun. poker , bandarq , aduq, domino qq , dominobet
. Semua permainan bisa dimainkan hanya dengan 1 ID. minimal deposit 10.000 ,- bonus turnover 0.5% dan bonus referral 20%. Bonus - bonus yang dihadirkan bisa terbilang cukup tinggi dan memuaskan, anda hanya perlu memasang pada situs yang memberikan bursa pasaran terbaik yaitu http://188.8.131.52/
Bola168. Situs penyedia segala jenis permainan poker online kini semakin banyak ditemukan di Internet, salah satunya TahunQQ merupakan situs Agen Judi Domino66 Dan BandarQ Terpercaya
yang mampu memberikan banyak provit bagi bettornya. Permainan Yang Di Sediakan Dewi365 Juga sangat banyak Dan menarik dan Peluang untuk memenangkan Taruhan Judi online ini juga sangat mudah . Mainkan Segera Taruhan Sportbook anda bersama Agen Judi Bola
Bersama Dewi365 Kemenangan Anda Berapa pun akan Terbayarkan. Tersedia 9 macam permainan seru yang bisa kamu mainkan hanya di dalam 1 ID saja. Permainan seru yang tersedia seperti Poker, Domino QQ Dan juga BandarQ Online
. Semuanya tersedia lengkap hanya di ABGQQ. Situs ABGQQ sangat mudah dimenangkan, kamu juga akan mendapatkan mega bonus dan setiap pemain berhak mendapatkan cashback mingguan. ABGQQ juga telah diakui sebagai Bandar Domino Online
yang menjamin sistem FAIR PLAY disetiap permainan yang bisa dimainkan dengan deposit minimal hanya Rp.25.000. DEWI365 adalah Bandar Judi Bola Terpercaya
& resmi dan terpercaya di indonesia. Situs judi bola ini menyediakan fasilitas bagi anda untuk dapat bermain memainkan permainan judi bola. Didalam situs ini memiliki berbagai permainan taruhan bola terlengkap seperti Sbobet, yang membuat DEWI365 menjadi situs judi bola terbaik dan terpercaya di Indonesia. Tentunya sebagai situs yang bertugas sebagai Bandar Poker Online
pastinya akan berusaha untuk menjaga semua informasi dan keamanan yang terdapat di POKERQQ13. Kotakqq adalah situs Judi Poker Online Terpercaya
yang menyediakan 9 jenis permainan sakong online, dominoqq, domino99, bandarq, bandar ceme, aduq, poker online, bandar poker, balak66, perang baccarat, dan capsa susun. Dengan minimal deposit withdraw 15.000 Anda sudah bisa memainkan semua permaina pkv games di situs kami. Jackpot besar,Win rate tinggi, Fair play, PKV Games
Update : It works if you run it on Edge or Chrome, but not on Firefox
I have the same problem (see my post here: https://forum.cogsci.nl/discussion/7713/osweb-error-when-using-jatos-in-firefox-browser#latest )
I am struggling with the same problem. Now I also asked someone using a mac to test my experiment and she gets the same error message on Firefox as the one Indiana posted + a different, but very similar one on Safari:
TypeError: o is not an Object. (evaluating '"data"in o')
I found some comments on this or similar problems in other forums, but they didn't really help me understand what causes the error and how to solve the problem.
Hi everyone! Sorry for the delay. One errer message caught me eye:
jatos.js not yet initialized. That's strange. Can you please share the JATOS .jzip of your experiment (not the .osexp)?
@annma I tried my experiment now a couple times again and I also get the "o is not an object" in Safari, but not always, some runs go fine, others show the error.
@Indiana Did you also update to the latest JATOS version and only encountered the problem then? That was the case for me, I also had no such problem before the update (and importing my experiment again for a different reason)... So I'm wondering whether it could have to do with that?
I don't know why but I can't link my jatos file. My brother opened the same topic on git-hub and someone named Kristian asked him the jatos file, if this you it's perfect because he succeed to send you the jatos file there ! @kri
@JaHa I'm using mindprobe to host my expe online. I guess they also did the last update like you few days/weeks ago.
:) Yes, the Kristian is me. I got it. I'll try to have a look now.
@Indiana @annma @JaHa Apart from the error message your studies work, don't they? Just tested them and I can click and proceed. Or is there something that does not work? I just want to know. The error message still worries me and I will have a closer look anyway.
Hi Kristian! Thank you so much for your help!
On Chrome, my study works just fine. On Firefox, however, I get the error message and then, after a couple of clicks, the experiment crashes and I get the following message:
A problem occurred: Errors occurred. See log for details.
@kri Yup it does work perfectly !
@Indiana , I think I found a fix. It seems to have been an issue with Webpack that is used to pack jatos.js since the last version 3.7.1. But can you please confirm that it works on your side. I made a fixed jatos.js and load it in your study from the assets:
Then if it works for you too I will to a new JATOS release (3.7.2) with the fixed jatos.js.
@kri, is this a fix I could replicate for my experiment? Or is it too complicated and you would need my zipped experiment as well?
@annma, you could replicate it for your experiment. But probably easiest is to wait for the new release. If it works for the other two (Indiana and JaHa) I will do the new version in one or two days.
But if you can't wait: Get the folder 'jatos' from the study zip I uploaded yesterday and put it in your study asset folder. Then, instead of loading
That should do it. You basically load your own jatos.js (the fixed one) instead of the one provided by JATOS.
@kri, thank you so much! I followed your instructions and it works! I don't get the error massage in Firefox any longer and neither does the experiment crash.
However, there seems to be a problem with transferring the data. At the end of the experiment, it says "Transferring you data. Please wait a few moments.", but it still says so after 5 minutes and no data is transferred to my JATOS server. This is only the case when I open a study link via Firefox. In Chrome, on the other hand, it works just fine. Do you think there might be a connection to the other problem or is this something different?
@annma Yes, happens with me too. I will investigate further.
@annma Actual I was mistaken, it doesn't happen with me. Can you send me your study so I can reproduce the problem on my side?
EDIT: Actually can you please send me a minimal reproducible example (so I don't have to click through 30 min of the study)?
@kri It works for me ! Thanks
I also have the same message than @annma at the end but it stays only for 2sec then the results are corretly transfered.
@annma Got your example study and could reproduce the issue. The problem only occurs with my Firefox if I have the Developer Tools open. I think I know the reason for the 'error': Some browsers (maybe only Firefox) if you want to see the source code (tab 'Debugger') reload the page internally to catch the page's source code. Chrome goes a different way: It doesn't show you source code until you reload the page manually. The thing with your study is that reloading is not allowed. So as soon as you open the Developer Tools' Debugger tab (maybe even when you open any tab) Firefox sends a second page load (that is not visible in the Network tab btw.). JATOS thinks it is a reload and finishes the study run with an error. Then all subsequent requests from your study, e.g. sending result data, fail with error 403 ' Study run is already finished'. For JATOS there is no way to distinguish between a 'real' page load and an internal Firefox load.
So, I think your study will run fine with your participants as long as they do not open Firefox's Developer Tools which is hopefully unlikely. But if you want to be on the safe side you can check 'Allow reload' in your component properties. This is also the way if you want to debug your study.
Hope this helps.
@Indiana Nice it works for you now. About the message you see in the end, "Transferring you data. Please wait a few moments.", if it disappears again and no error occurs in the browser's console, then this is the way it should be. This message only gets shown if the component finishes but data is still to be send. Especially if you have a lot of data or a slow internet connection you will see this message a lot.
So my plan is to make a new release tomorrow (v3.7.2) with the fix in jatos.js.
@kri Don't wish me the best, YOU are the best ;)
Thanks again for your help and the fix !
@kri Hi Kristian,
I checked 'Allow reload' and now it works even in my Browser. I will do a couple more test runs with some colleagues now, but I think that solved the problem.
Thank you so much for your time and effort!
@annma @Indiana @JaHa I had to put release to version 3.7.2 on hold. The Firefox fix seems to cause a problem in Chrome. I have to investigate further.
@annma @Indiana @JaHa Okay, fixed it: version 3.7.2 is released (again). At least on my side it's working in FF and Chrome locally and remote.
@kri It works for every browser now, thanks a lot !
You're the best
I still get the same error report from participants using Firefox. I recently downloaded the last version of OpenSesame. Should I update something else to fix the error?
What's your JATOS version? If less than 3.7.4, please upgrade.
Sure, I am using 3.7.1! Sorry for not checking before asking. I will ask to update it.