does it got resolved? i am facing same issue

Still not solved? we have the same issue using mabs 9.0, it didn't compile for iOS

Hi,

I hit this exact 'OutSystems-Swift.h' file not found error too (in my case it surfaced on the Firebase Analytics plugin, but it's the same root cause and it can land on Cloud Messaging just as easily).

I've had a bit of help from Claude, and managed to wiggle my way out of that mess. When I found this thread I asked it to adjust to other issues like this.

Important note: I tested the original fix exclusive to Firebase Analytics, and it worked. If this fix fails, it's likely either MABS evolved, or the adjustment Claude did for your scenario is not complete. Let me know if that's the case and we can work on it - while I have this project saved.

Here's the full diagnosis and fix (AI generated):

Why it happens — and why it isn't specific to one plugin

Several OutSystems plugins ship an Objective-C CDVPlugin shim that bridges to their Swift implementation by importing the app's generated Swift header:

#import "OutSystems-Swift.h"

That line assumes the app's Swift module is named OutSystems. On current MABS (with Xcode 26.x), the app's Swift module is named after the application instead — e.g. an app called My App - Mobile gets the module My_App___Mobile, so the generated header is My_App___Mobile-Swift.h, not OutSystems-Swift.h. The hard-coded import then points at a header that's never produced:

…/Plugin.m:7:13: fatal error: 'OutSystems-Swift.h' file not found** ARCHIVE FAILED **

It shows up on whichever plugin happens to contain that Objective-C bridge. Some plugin versions are pure Swift (no Obj-C shim → unaffected); others carry the Obj-C bridge (affected). That's why one person sees it on Analytics and another on Cloud Messaging — it's the same defect, just a different file importing OutSystems-Swift.h.

Note the generated -Swift.h aggregates all of the app target's Swift symbols, so a single shim fixes every affected plugin at once.

Fix: a tiny hook plugin that adds an OutSystems-Swift.h shim

The file I uploaded includes 3 files which change the compilation on MABS a tiny bit.

This after_prepare hook scans the iOS source for any file that imports OutSystems-Swift.h and drops a shim header of that name next to each one. A quoted #import searches the including file's own folder first, so the shim is always found, and it forwards to the app's real generated header. Works for Analytics, Cloud Messaging, or any other plugin with this bridge.

How to add it

• In Service Studio: Data → Resources → Import Resource… and add the zip to the module that holds your Extensibility Configurations.
• In that module's Extensibility Configurations, reference it:
  {
      "resource": "cordova-plugin-os-swift-header-fix.zip",
      "plugin": {
          "resource": "cordova-plugin-os-swift-header-fix"
      },
      ....
  }

A note for the OutSystems team

The Objective-C bridge in the affected plugins hard-codes #import "OutSystems-Swift.h", which only works when the app's Swift module is literally named OutSystems. Under current MABS the module name follows the app name, so the fallback breaks. Please make the bridge independent of a fixed module name (e.g. import the real -Swift.h, compile plugin Swift into a deterministically named module, or document a supported way to pin the iOS Swift module name). Happy to share build details.