Autonomous Single App Mode (ASAM) and TestNAV App

Thanks for everyone's feedback! Does anyone know what "bug fixes" 1.3.2 has over 1.3.1 TestNAV? Gotta love Pearson updating their app a week or so before we all need to test!

Spoke with people at PARCC and they said that there is only minor changes from 1.3.1 to 1.3.2. Testing can work properly on version 1.3.1.

funny I did a successful infrastructure test last week with ver 1.3.1 updated to 1.3.2 this week and tested it this morning and it does not work properly, I am now getting "Error 3044: TestNav can not lock the device. Please contact your proctor" nothing changed other than the update from Pearson

Just to update you guys... I was on with Pearson support for over 2 hrs today... Turns out with Version 1.3.2 you need to have guided access enabled. The hope is they will correct this in their next release

Pearson is a joke. ASAM has been the recommended way to test since last spring and it has yet to work on their end.

Did you remember to change the app version under apps to reflect that this is 1.3.2 and not 1.3.1?

yeah actually as part of troubleshooting I've recreated the entire profile

Also seeing "Error 3044: TestNav can not lock the device. Please contact your proctor" when trying to use ASAM in our PreProd testing (Casper 9.65, iOS 8.1.3, TestNav 1.3.2). In lieu of a TestNav fix (e.g. 1.3.3), it looks like a Config Profile with Single App Mode payload pushed out to groups at testing time (and then removed) might be a less than optimal workaround?

I have successfully tested a few this morning. All are at 8.1.3, some had updated from 1.3.1 and a some installed 1.3.2 fresh. All starting without the error 3044. The only one where I saw the issue was one device that was not in my "test" group and therefore did not receive the profile for ASAM. Once I added it to the profile it launched the TestNav app successfully.

The inconsistent results are ridiculous... What version of JSS are you running?

We did upgrade to 9.6.5 last night.

yeah we are on 9.6.5 as well and tested with freshly wiped iPads and still received the error 3044....

Not sure if coincidental, but I did remove the TestNav application completely (vs just updating version number) and added again to ASAM Config Profile (didn't recreate profile) and it seems to be working. We'll see if it still works in the AM ...

Have any of you guys started testing yet? Are you running into any ASAM issues with the live test?

Started testing this week with our computer labs and starting on iPads next week. With IOS 8.2 supposedly launching next week; I am doing some beta testing on an iPad 2 running IOS 8.2 Beta 5. TestNav 1.3.2 is still broken from ASAM but will work with Guided Access. I am going to see tomorrow how TestNav 1.3.1 functions on IOS 8.2 and will update my findings here.

Good luck everyone!

This was posted to CDE (Colorado Department of Education) site on some PARCC lessons learned:

Chromebook and iPad TestNav App (Error 2008) – Memory Limits If a device is used by students for instruction or other purposes, it may be good practice to restart the devices prior to testing to ensure that there are no apps running in the background •

We have been testing the last couple of weeks with MacBooks an iPads sucessfully. At first I made a Configuration Profile to use the Single App Mode payload, but then I read in Pearson's documentation to use "Autonomous Single App Mode apps" in the Restrictions payload which actually works better because it automatically puts TestNav into single app mode on demand rather than pushing out the policy each time to enable/disable it. Machines do have to be supervised. Another couple of requirements are to turn off "Check Spelling" and "Predictive" under General > Keyboards. I am using version 1.3.2 of TestNav and IOS version 8.xx.

And yes, restart the device prior to testing each time to clear any proccesses that may be running.

Also wanted to mention that the app brings you to a generic page. If you are doing a trial test, you must select "PARCC Training" from the "Select your Test" drop down box.

@msnowdon is ASAM working for you? What version of the JSS are you running?

Within the profile settings you can now disable predictive text, auto correct, spell check, and definition lookup.

We are using JSS 9.62 but I want to upgrade to 9.65 because I read that you can change the Keyboard settings from a policy now, rather than manually doing it to all machines.

We have AirSecure Test deployed to our grades 3-5 iPads. We have them all in a testing profile that has all of our restrictions but enables the app store. For some reason the app store must be enabled for the app to enter ASAM. We are running 9.65 but we haven't disabled spellcheck and others because it would affect all other apps as well.

One thing we did find which I'm sure others have found is that when testing, Auto screen lock needs to be set to NEVER. Otherwise if the screen locks it screws up the test and the device has to be rebooted.

Those are options in 9.65. Good to hear that ASAM *might* work this time. I've heard a lot of inconsistent reports that it works or it doesn't.

We are still having mixed results with ASAM. A majority of students it is working for a small percentage it is not. No rhyme or reason

We just started this morning and ASAM didn't work for any of our students.

We started today and it worked for about 98% of ours. The few it did not work for had some accessible features turned on - once we stopped that and reinstalled they were OK. Are all of your students supervised? From a Prestage enrollment? or from configurator?