MAC OS Warning Intel

I get a warning when I open XCTU on my MacBook Pro with M1 processor. It states that XCTU may no longer run on non-Intel machines. Will there be some kind of rebuild to address this?

Thank you,

Z

No, the XBee Studio is the replacement application.

Following up — the “use XBee Studio instead” answer doesn’t actually solve the
problem, for two concrete reasons.

My setup on macOS (Apple Silicon): a few XBee3 modules, plus several legacy XBee S2C
modules used as Zigbee repeaters.

1. XBee Studio is Intel-only too. Its own system requirements state “macOS 10.14
or later (64-bit Intel processors only)”. XCTU triggers the macOS “Intel-based app
support ending” warning because it’s an x86_64 build running under Rosetta 2 — and
XBee Studio is exactly the same. Apple removes Rosetta 2 in macOS 28 (fall 2027), so
both apps stop launching on the very same date. Migrating from one Intel-only app to
another Intel-only app does not address the architecture problem at all.

2. XBee Studio won’t even open my S2C modules. When I select an S2C, it hard-stops
with: “XBee Studio does not support devices with hardware version 0x2E.” So for legacy
S2C / Series-2 hardware, XCTU is the only tool — and it’s precisely the one being
left to break on Apple Silicon. S2C owners are left with no supported path whatsoever.

So, two questions for Digi:

  • Is there a roadmap for a native Apple Silicon (arm64) tool to configure XBee3 RF
    modules on macOS before the macOS 28 / Rosetta 2 cutoff?
  • For legacy S2C / Series-2 modules specifically, what is the supported
    configuration path on Apple Silicon Macs once Rosetta 2 is gone, given that XBee
    Studio explicitly rejects them?

Thanks.

I still get the same warning opening XBeeStudio.

Please use the Feedback option in the XBee Studio to report your concerns. Doing so will allow the folks who are directly responsible for the XCTU and XBee Studio application aware of your concerns.

The XBee Studio only supports the XBee 3 products and newer. The S2C are considered Legacy and veracious versions of it have already gone EOL.

While Eng. had not yet made any plans for the non Intel based systems, there is still plenty of time for that to change. What I would suggest is that you submit the feedback as suggested but also include the total number of the XBee S2C modules you are working with.