-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New version #32
Comments
Hey, i would love if you could release a new fix for the new version 3.7 |
up |
When will the patch for version v3.7.0.682 be released? |
@rmdhfz @apaolino96 @Zwilgmeyer @HENSOUMON |
@wxnnvs |
ah, that sucks |
I fixed it if anyone wants I can guide them hmu on telegram |
New version is patched. Will release it ASAP. I'm really sorry for the long delay |
Hi there @nxvvvv . Thanks for getting back to us. I would love to discuss this and some of the concerns raised by Pinkestflamingo about detectability through cache scrubbing. Is there any way to communicate directly? I'd be happy to pay for the privilege. And I will of course resume my monthly support once the project is back up.
|
Y'all should check out my project as well |
Well... I wouldn't recommend. I ended stuck in a red screen with: "You're using a modified version of the safe exam browser" or something like that. |
I'm waiting for version 3.7 too |
I never had this issue, what version of SEB do you use? |
SEB 3.7.1 it was on a exam on smartlearn. If I had time, I would have made a picture, but in the moment I had other problems. And I wasn't able to create an issue on your repository otherwise I would already have made one. |
I tested SEB 3.7.1 with all their demo exams, never had a problem. BTW: You can now create issues on my repo |
Can I still use the old version which this repo patch supports? Does it force updating? I'm new to this SEB stuff ((: |
With my experience, SEB doesnt update, altough your school may require you to use the old version. |
Hi. SEB has released a new version. Any chance you could release a new fix?
The text was updated successfully, but these errors were encountered: