quasarframework/quasar · warning

Also, disable HTTPS from quasar.config file > devServer > se

Error message

Also, disable HTTPS from quasar.config file > devServer > server > type: 'https'

What it means

Third line of the missing-AppDelegate.m warning group: since the SSL patch could not be applied, the app will reject the dev server's self-signed certificate, and Quasar advises disabling HTTPS via quasar.config file > devServer > server > type.

Source

Thrown at app-vite/lib/modes/cordova/config-file.js:136

  }

  #prepareAppDelegate(node) {
    const appDelegatePath = this.#ctx.appPaths.resolve.cordova(
      `platforms/ios/${node.text}/Classes/AppDelegate.m`
    )

    if (!fs.existsSync(appDelegatePath)) {
      warn()
      warn()
      warn()
      warn()
      warn(
        "AppDelegate.m not found. Your App will revoke the devserver's SSL certificate."
      )
      warn(
        'Please report the cordova CLI version and cordova-ios package that you are using.'
      )
      warn(
        "Also, disable HTTPS from quasar.config file > devServer > server > type: 'https'"
      )
      warn()
      warn()
      warn()
      warn()
    } else {
      const tamperedFile = {
        name: 'AppDelegate.m',
        path: appDelegatePath,
        originalContent: fs.readFileSync(appDelegatePath, 'utf8')
      }

      // required for allowing devserver's SSL certificate on iOS
      if (
        !tamperedFile.originalContent.includes(
          'allowsAnyHTTPSCertificateForHost'
        )

View on GitHub (pinned to 4841521b5f)

Solutions

  1. Set devServer > server > type to 'http' in quasar.config (or remove the https override) so no certificate patch is needed.
  2. Restore the standard iOS project layout (re-add the ios platform) so the patch can be applied, then re-enable HTTPS.
  3. If HTTPS is mandatory, manually add the certificate-acceptance code (allowsArbitraryLoads / handling of the ATS exception) to AppDelegate.m yourself.

Example fix

// quasar.config.js — before
devServer: { server: { type: 'https' } }
// after
devServer: { server: { type: 'http' } }
Defensive patterns

Strategy: fallback

Validate before calling

// quasar.config.js guard — avoid https when the iOS patch may be unavailable
const fs = require('fs');
const canHttps = fs.existsSync('src-cordova/platforms/ios/App/App/AppDelegate.m');
module.exports = function (ctx) {
  return { devServer: { server: { type: canHttps ? 'https' : 'http' } } };
};

Prevention

When it happens

Trigger: Emitted with errors 132/133 by #prepareAppDelegate during HTTPS Cordova iOS dev when AppDelegate.m is absent; consequence is white screen/connection failure in the iOS app against the https dev server.

Common situations: Developer keeps type:'https' while the patch failed and then sees the iOS app unable to connect; CI containers where the iOS platform was added with an incompatible cordova-ios.

Related errors


AI-assisted analysis of quasarframework/quasar@4841521b5f (2026-08-30). Data as JSON: /api/errors/0ed8ad0531e7c7fc. Report an issue: GitHub.