Imagine Learning Español iOS app release notes

2.100 – February 14, 2017

This release fixes a critical field issue related to video playback on iPads introduced with the iOS 10 release. Additionally, we're introducing performance enhancements and tools to assist with network diagnostics and troubleshooting.

This release will be submitted only to the App Store (iOS).

This release introduces system requirement changes for the 2017-2018 school year.

The Imagine Learning Español web app that runs in browsers with the Unity Web Player plugin (Firefox, Safari, Internet Explorer) will no longer be updated. We encourage you to switch to a Windows or Mac standalone app, or use the Imagine Learning Español web app in a Chrome browser ( We plan to add support for newer versions of Firefox and Edge in future releases.

If you continue to use the 2.4.80 version of the app in a browser, you can expect to experience these consequences:

  • Students won't receive any new curriculum
  • Students who use Imagine Learning Español and switch between devices with different app versions may lose their place in the sequence

New Features

Network latency health tool

We've added a new Network Latency Health tool to help you troubleshoot interruptions to student sessions because of network-related issues. You can enable the tool and leave it on for up to 7 days and submit a report to be reviewed by Imagine Learning at any time during that window.

To access the tool, log in to the app, click Pause, then click Troubleshooting, and click Network Health. Click Enable to start the tool.

Error prompts

We've reduced network-error prompts that are caused by server-side issues, and to make troubleshooting easier, we've added more detail to the error message displayed when you experience delayed student session issues.

App settings

You can now access settings from the login screen that allow you to determine how you will cache media, specify the language students hear when you start activities from the Activity menu, or enable logging for troubleshooting purposes.

Single instance Windows app

We now ensure that only one instance of the Windows app is allowed to run; clicking the icon will not launch the app again if it is already running.

Optimized memory management

We've made improvements to the way we manage memory to provide a more stable user experience.

Interface improvements in Decodable Books

You can now swipe pages backwards in Decodable Books.


Clever integration with Chrome Web Store app

If the Chrome Web Store app is installed on a device, you can now launch that app from the Clever student portal. Previously, the web app was launched in a Chrome browser.

Interface improvements to loading screen

The Booster loading screen now indicates loading status more accurately, and also includes a status message.


  • We've fixed a critical field issue related to the iOS 10 release that caused video activities to lock up on iPads.
  • We've resolved a known issue that caused an error message associated with the caching mode setting. The pre-caching mode now functions again after updating from previous versions.
  • We've resolved a known issue associated with incorrect media folder permissions on Mac OS X. Media folder permissions on Mac OS X and macOS are now set for all users.

Known issues

Video pause functionality

Some videos continue to play on iOS devices if you first pause the app mid-video and then press the Home button on the device.

To work around this issue

  1. Force close the Imagine Learning Español app.
  2. Re-launch the app.

Older graphics cards can't run the app

This app release introduces some hardware system requirements changes. As a result, devices without graphics cards capable of supporting OpenGL 2.0 may have issues running the Imagine Learning Español app.

To work around this issue

  1. Run the 2.4.80 version of the Imagine Learning Español app on older devices.

Imagine Learning Español Windows app and Site Codes

Students using an unmanaged Imagine Learning Español Windows app may be asked to enter a Site Code as part of the authentication process when they first launch the app.

To work around this issue

  1. Manually enter the Site Code before you launch the app. This is only necessary with the first launch.