seb-mac

seb-mac copied to clipboard

I know this is not a lot to go on, but hoping for some advise. We have used JAMF to configure SEB in the past, but did not use SEB during COVID-19 (so have not tested for some releases) and are doing some testing and validation of our procedures prior to fall term.

When launching SEB on an iPad configured via plist in JAMF, SEB shows a blank (white) screen and then exits with no message. This happens on a "stock" configuration profile exported from SEB installed through the App Store. We have experimented with some of the settings (primarily related to single app mode as well as trying different start url).

I guess this is partly a bug report and partly a request for any troubleshooting suggestions. I will attach one of the plists we have tested here, in case that is helpful. esfcom-seb-2.plist.zip

I'll try to reproduce this issue, as it seems it happens with any configuration, it might be a general problem with MDM configuration in SEB 3.1. I think we tested it last with SEB 3.0 and were not aware of changes in this code in 3.1, but probably some change broke MDM configuration in this version.

Thank you! As far as I can tell it is crashing with any config. But the same config when not deployed via MDM seems to work fine. Please let me know if there is anything we can do to help with testing.

Before releasing SEB 3.1.1 for iOS, I briefly tested reconfiguring with MDM (Jamf Pro) and it was working with a very simple config:

<dict>
	<key>startURL</key>
	<string>https://safeexambrowser.moodle.ch/lms/</string>
</dict>

Maybe the reason for the crash in SEB 3.1 was fixed in SEB 3.1.1, or it crashes with a larger configuration or with specific keys. Please test it again with SEB 3.1.1 and if you still encounter a crash, send me the configuration you use.

I don't know if that was clear, you just need to paste setting key/values to the Jamf app configuration text box which are different than the SEB default values. When I have time, I will add an export option in SEB to just export the key/values which are different than the default values. Maybe large configurations create issues when used with MDM.

Also when you encounter crashes, activate sharing crash logs in Settings / Privacy / Analytics & Improvements / Share iPad Analytics / Share With App Developers. I receive crash logs from devices where this is active, some issues I was able to solve just with such anonymous crash logs. You can also install the iOS TestFlight beta version (which gets updated whenever there is a new beta). There you can also share issues directly and add a short description, so I could figure out that it was this MDM issue.

I am having the same issue. We are using Securly MDM and I have tried making the plist file in the app (3.1.1) and having Securly push the config to iPads. I have tried on both iPad Pros (5th gen 12.9 inch) and regular iPads (9th gen) Same issue as OP, blank screen then crash to home screen with no error message. Using the same config but saving the file as a SEB file instead does work if I place it on a web server and have the iPads visit the link, but when deploying the plist file via MDM, which would be optimal, it does not work. I agree with OP that it seems to crash with any config as I tried several different combinations of settings as well to see if one particular setting was causing it, but have not gotten a single plist file to work via MDM. Looks like it is not just JAMF.

Ok, I tried it with the plist provided by @seangirard (don't know if I missed to do that before), and it also crashed. I found the issue and it will be fixed in the next release (3.1.2).

As a workaround in the meantime you can remove the entry for prohibitedProcesses from your settings (use a text editor or similar). These are anyways irrelevant for the iOS version.

	<key>prohibitedProcesses</key>
	<array>
		<dict>
...
		</dict>
		<dict>
...
		</dict>
...
	</array>

Removing that section did indeed solve the problem perfectly. A thousand sincere thank you's from me to you! We are testing tomorrow on 150 iPads and you just saved me the time of having to download the SEB file to every one manually.

This should be fixed since SEB 3.3.