Skip to main content

Troubleshooting: DioException (400 Bad Response) During Swif Installation

Overview

When installing the Swif Desktop application on macOS or Windows, you may encounter the following error:

"Error DioException [bad response]: This exception was thrown because the response has a status code of 400 and RequestOptions.validateStatus was configured to throw for this status code."

This error occurs during the enrollment step of the installer and prevents the device from completing registration with Swif.


What Causes This Error

The Swif Desktop installer needs to retrieve your device's serial number during enrollment. In some cases, other security or MDM software already installed on the device (such as Rippling, SentinelOne, or similar endpoint protection tools) can block the installer from reading this information. Without a valid serial number, the enrollment request fails with a 400 (Bad Request) error, and the device will not appear in your organization's Swif dashboard.


How to Fix It

Use the Silent Installer (Recommended Workaround)

The Silent Installer bypasses the interactive enrollment flow that requires the serial number lookup, allowing the device to enroll successfully even when other security software is present.

To get the Silent Installer:

  1. Contact your IT administrator or IT security team and request the Swif Silent Installer for your platform:

    • macOS — Silent PKG installer

    • Windows — Silent MSI installer

  2. Your IT admin can download the Silent Installer from the Swif Admin Dashboard under the device enrollment section.

  3. Follow your IT team's instructions to run the installer. Note that admin/root privileges are required.

💡 For a full comparison of all Swif enrollment methods by platform, see: Swif Enrollment Methods for All OSs

For IT Administrators

If your end users report this error, the most reliable resolution is to provide them with the Silent Installer package:

Platform

Silent Installer

How It Runs

macOS

Silent PKG

Deploy via terminal with sudo, or push through your existing MDM

Windows

Silent MSI

Deploy via command line or group policy; runs in SYSTEM context

The silent installer does not depend on the interactive serial-number retrieval step, so it works even when third-party endpoint agents are present on the device.

Still Need Help?

If you continue to experience installation issues after using the Silent Installer, please contact Swif Support with the following details:

  • Your operating system and version

  • The error message or screenshot

  • Any other security or MDM software installed on the device

  • Your device serial number (if known)


Did this answer your question?