Skip to content
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

SEB not working (old), crashing on iOS 17 (new issue) #321

Closed
AnnePH opened this issue Sep 19, 2023 · 23 comments
Closed

SEB not working (old), crashing on iOS 17 (new issue) #321

AnnePH opened this issue Sep 19, 2023 · 23 comments

Comments

@AnnePH
Copy link

AnnePH commented Sep 19, 2023

We are using Safe Exam Browser in our quizzes but when some of our iPad updated to iOS 17.0 this error was produced:
image
Does anyone have the same experience? Do we have a workaround for it? We cannot downgrade our iPads though...

Your feedback and suggestion is highly appreciated.

Thanks! 😊

@danschlet
Copy link
Member

danschlet commented Sep 19, 2023

We are waiting for Apple App Store review to approve the SEB 3.3 update which will run on iOS 17 without having to change settings. For now you can either change the setting below manually in your SEB settings or use the SEB 3.3 release candidate version using TestFlight with this link.

You can include or change the setting allowiOSBetaVersionNumber with the value 17 in an unencrypted SEB configuration file:

	<key>allowiOSBetaVersionNumber</key>
	<integer>17</integer>

Because they had bugs in earlier iOS beta versions which made SEB insecure (once the single app mode didn't work at all), we had to introduce this setting. Unfortunately the release of the 3.3 update got delayed last week.

But with this setting the current version will run on iOS 17.

@AnnePH
Copy link
Author

AnnePH commented Sep 19, 2023

I appreciate the fast response on this. We already tried updating the settings and it works. We'll just have to wait for the release of SEB 3.3.

@jjack2003
Copy link

We have some students who have updated to iOS 17, and cannot open tests in the browser. It brings up the red screen. We verified the student was on version 3.3 through our MDM, but after a hard restart, we are still having the issue. Any thoughts or suggestions.

@danschlet
Copy link
Member

There seems to be an issue on specific devices using iOS 17. Frequent crashes occur when in AAC and clicking into or starting to enter text in any text field (alerts, text fields in other app UI, text fields on a website displayed in WKWebView or UIWebView). This doesn't happen with the same version of SafeExamBrowser running on iOS 16.6.1 or iOS 15.6.1.

It also doesn't happen on other devices. Until now I tried it on four iPads, and it seems it happens on iPads with cellular, not on iPads with WiFi only. I reported this to Apple, as it might be an iOS 17 issue.

Can you try to find out if students with these issues have iPads with Cellular? Or in general on which devices it happens?

@danschlet
Copy link
Member

Step-by-step instructions to reproduce:

  • Install SafeExamBrowser 3.3 from the App Store.
  • In the field "Enter the URL of an institution which supports SEB" enter "let.ethz.ch" (without quotation marks).
  • Alternatively open the page https://safeexambrowser.org/exams/ in Safari and proceed as below.
  • On the newly displayed page "Exam Portal" click on the first link SEB Demo Exam, confirm app self lock.
  • Tap the quit button in the lower right
  • Either SEB will crash immediately, otherwise in the alert asking for the quit password (which is in this case "quit") start typing.
  • Observe if a crash is happening.

@jjack2003
Copy link

All of our student iPads are wifi only.

@danschlet
Copy link
Member

Then it might be another reason, why it happens on some devices but not on others. For you, does it happen to all students which are updated to iOS 17?

@jjack2003
Copy link

I have only heard from about 15, so far. We 390/1500 updated to 17 at this time. I will have to see how many more report the issue. It may very intermittent. I just set up a test device, newly enrolled with iOS 17 and version 3.3, it doesn't seem to be having the issues. I am updating another device, just as a student would, and I will see how that one works. I appreciate the quick responses. I will keep you updated.

@danschlet
Copy link
Member

Thank you for keeping me updated. I've been trying to analyze this issue the last two days since we realized it. Somehow it didn't occur while testing on iOS 17 beta versions (or on the devices we used then).

@AnnePH
Copy link
Author

AnnePH commented Sep 25, 2023

We also encountered a red screen, when during the exam, the student forcibly restarted the iPad. We resolved the red screen issue by inputting the quit password.

@rataplanbe
Copy link

Step-by-step instructions to reproduce:

  • Install SafeExamBrowser 3.3 from the App Store.
  • In the field "Enter the URL of an institution which supports SEB" enter "let.ethz.ch" (without quotation marks).
  • Alternatively open the page https://safeexambrowser.org/exams/ in Safari and proceed as below.
  • On the newly displayed page "Exam Portal" click on the first link SEB Demo Exam, confirm app self lock.
  • Tap the quit button in the lower right
  • Either SEB will crash immediately, otherwise in the alert asking for the quit password (which is in this case "quit") start typing.
  • Observe if a crash is happening.

If I try this and I want to login in the exam, I have a crash. If I reopen SEB I have a red screen. If I want to put te word 'quit' in the textfield in the red screen, the app crashed. We are using IOS 17.0.1

@Basti8619
Copy link

Afbeelding (2)
Just found this thread. Every iPad updated to iOS 17 now has SEB version 3.3 but none can use it with bookwidgets. They get this message. Something to do with settings? Never had any problems before on older iOS versions.

@danschlet
Copy link
Member

danschlet commented Sep 28, 2023

We assume there is some iOS 17 change or bug involved, as there are devices with iOS 17 where it works perfectly, on other devices it crashes regularly, mostly when tapping or displaying text input fields. And on the same devices it doesn't happen with iOS 16 or 15. So this is some mysterious combination of iOS 17 and some device settings or similar. We're trying to find out what we can do in SEB to prevent this suspected iOS 17 issue crashing SEB.

@rataplanbe
Copy link

Afbeelding (2)
Just found this thread. Every iPad updated to iOS 17 now has SEB version 3.3 but none can use it with bookwidgets. They get this message. Something to do with settings? Never had any problems before on older iOS versions.

What happens if you do an hard reset on the device? Normally, the message is gone. We can run Bookwidgets, but the question type 'Textfield' don't work.

@Basti8619
Copy link

What happens if you do an hard reset on the device? Normally, the message is gone. We can run Bookwidgets, but the question type 'Textfield' don't work.

I will try it out with a test tablet. Can hardly reset over a 1000 tablets though. Hoping on a fix!

@danschlet
Copy link
Member

On one of my devices this issue seems to no longer to happen after updating it to iOS 17.1 Beta 2. Maybe someone can confirm that as well.

@Basti8619
Copy link

Basti8619 commented Oct 6, 2023

I tested SEB on several iPads. 2 for each.

The ones on 17.0 had no problems.

The ones on 17.1:
1 has no problem.
the other couldnt open SEB. After reinstalling SEB it could but when i touched a textfield it crashes.

The ones on 17.2:
1 has no problem.
1 cannot touch a textfield aswell.

I assume this is the known issue. When can we expect some news?

@danschlet
Copy link
Member

I now got feedback from Apple that they found the bug actually responsible for this. It should be fixed in a later iOS 17.1 beta version.

There was a related bug in Guided Access which is already fixed in the current iOS 17.1 beta. Maybe this fix makes the other issue appear less often.

But we will have for the full fix in iOS 17.1.

@Basti8619
Copy link

I now got feedback from Apple that they found the bug actually responsible for this. It should be fixed in a later iOS 17.1 beta version.

There was a related bug in Guided Access which is already fixed in the current iOS 17.1 beta. Maybe this fix makes the other issue appear less often.

But we will have for the full fix in iOS 17.1.

Superb, thank you!

@danschlet
Copy link
Member

Ok, so in the meantime we found the likely reason why it these crashes happen only on some devices and not on others: If Guided Access is enabled (iOS Settings / Accessibility / Guided Access), then these crashes happen in SEB with iOS 17 on our test devices (even though Guided Access itself is not being used with SEB).

Apple fixed the issue in iOS 17.1 (developer?) beta 3.

@jjack2003 @Basti8619 @rataplanbe can you confirm that on the devices these crashes happen Guided Access is enabled in Settings? Do they still happen when you disable Guided Access. This is what I confirmed on two test devices.

If this is reason is confirmed, then you can either wait for iOS 17.1, install beta 3 or disable Guided Access for the meantime.

@danschlet danschlet changed the title SEB not working on IOS17 SEB not working (old), crashing on iOS 17 (new issue) Oct 16, 2023
@Basti8619
Copy link

Ok, so in the meantime we found the likely reason why it these crashes happen only on some devices and not on others: If Guided Access is enabled (iOS Settings / Accessibility / Guided Access), then these crashes happen in SEB with iOS 17 on our test devices (even though Guided Access itself is not being used with SEB).

Apple fixed the issue in iOS 17.1 (developer?) beta 3.

@jjack2003 @Basti8619 @rataplanbe can you confirm that on the devices these crashes happen Guided Access is enabled in Settings? Do they still happen when you disable Guided Access. This is what I confirmed on two test devices.

If this is reason is confirmed, then you can either wait for iOS 17.1, install beta 3 or disable Guided Access for the meantime.

Seems to be working. Have yet to confirm on multiple devices.

Thanks for this solution.

@jjack2003
Copy link

Is anyone else having compatibility issues with IOS 17.3?
Image

@azzazz280
Copy link

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants