Skip to main content

This page gathers the main support paths for students and instructors using Avida-ED.

Common starting points​

Help videos​

Classroom support workflow​

When something goes wrong in a class setting, the fastest sequence is:

  1. Confirm everyone is using the same app/version.
  2. Retry the task with the same browser and lesson steps.
  3. Use the troubleshooting checklist below.
  4. Report persistent issues to Avida-ed-development@googlegroups.com.

Troubleshooting​

Use this checklist when Avida-ED does not launch or assignment workflow steps fail.

If the app does not launch​

  • Confirm you started from Launch Avida-ED 4.
  • Reload once in the same tab.
  • Try a hard refresh:
  1. Windows/Linux: Ctrl + F5 or Ctrl + Shift + R
  2. macOS (Chrome/Firefox): Cmd + Shift + R
  3. macOS (Safari): Cmd + Option + R
  • Try a current desktop browser.
  • Check whether privacy tools or pop-up blocking interfere with the app.

If a classroom activity behaves unexpectedly​

  • Confirm all students are using the same version.
  • Make sure students are not changing more than one variable at a time.
  • Re-run the same setup once to check reproducibility.
  • Compare assignment steps with:
  1. Curriculum
  2. Lab Manual
  3. Model Lessons

If students cannot save or export files​

  • Confirm device download permissions.
  • Check browser download-block settings.
  • Verify the expected file download location.

Downloads​

For offline or legacy versions, use Download.

Reporting problems​

Every useful report should include:

  • Avida-ED version (for example 4.0.33)
  • browser and operating system
  • whether the issue happened on one device or many
  • exact step where the issue appeared
  • expected behavior vs actual behavior

Helpful evidence​

If your course/institution permits it, include:

  • screenshot of the error state
  • short screen recording
  • exact lesson/assignment step that triggered the issue
  • whether reload changed the result

Fast reporting template​

  1. I was using Avida-ED <version>. (for example 4.0.33)
  2. I was working in <browser + version> on <device/OS>.
  3. I did these steps: <step 1>, <step 2>, <step 3>.
  4. I expected: <expected behavior>.
  5. I observed: <actual behavior>.
  6. I retried and the result <did/did not> change.

For full reporting guidance, use the sections on this page and contact Avida-ed-development@googlegroups.com with the template above.