# Xojo and macOS 27.2 - An Important Compatibility Update/?

**URL:** <https://ifnotnil.com/t/xojo-and-macos-27-2-an-important-compatibility-update/4918>\
**Category:** Other\
**Created:** [18 November 2026 10:03 UTC](https://ifnotnil.com/t/xojo-and-macos-27-2-an-important-compatibility-update/4918 "2026-11-18T10:03:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarkusWinter](https://ifnotnil.com/user_avatar/ifnotnil.com/markuswinter/32/32_2.png) [@MarkusWinter](https://ifnotnil.com/u/MarkusWinter)\
**Post date:** [18 November 2026 10:03 UTC](https://ifnotnil.com/t/xojo-and-macos-27-2-an-important-compatibility-update/4918/1 "2026-11-18T10:03:34Z")

</div>

> **[Xojo and macOS 27.2: An Important Compatibility Update](https://forum.xojo.com/t/xojo-and-macos-27-2-an-important-compatibility-update/89225)**
>
> Originally published at: Xojo and macOS 27.2: An Important Compatibility Update – Xojo Programming Blog If you are running a Xojo release earlier than 2026r3 under macOS 27.2, or your users are running an app created with one of those earlier...

Does this make sense? Or is that only half the truth?

If it is true shouldn’t Apple’s own Apps be affected too? Eg old Apple apps running on macOS 27.2 show the same problem?

Or is it more like “version as string” again?

Anyone knows more about it?

---

<div class="post-metadata">

**Author:** ![bgrommes](https://ifnotnil.com/user_avatar/ifnotnil.com/bgrommes/32/2651_2.png) [@bgrommes](https://ifnotnil.com/u/bgrommes)\
**Post date:** [18 November 2026 12:44 UTC](https://ifnotnil.com/t/xojo-and-macos-27-2-an-important-compatibility-update/4918/2 "2026-11-18T12:44:54Z")

</div>

If I were Xojo I would lean into this explanation to sell licenses.

From what’s been said here before it was probably avoidable, but who can say. It’s like trying to get the US administration to give (or get the the bottom of) the cause of the air stop last Friday … “nice air traffic system you got there, be a shame if something happened to it” seems to be more the subtext. In both cases, I think they did it because (1) they could and (2) they are clowns. Same principle here.

---

<div class="post-metadata">

**Author:** ![npalardy](https://ifnotnil.com/user_avatar/ifnotnil.com/npalardy/32/10_2.png) [@npalardy](https://ifnotnil.com/u/npalardy)\
**Post date:** [18 November 2026 13:10 UTC](https://ifnotnil.com/t/xojo-and-macos-27-2-an-important-compatibility-update/4918/3 "2026-11-18T13:10:30Z")

</div>

I would expect old versions of Apple Apps to behave badly IF this were the root cause

I do suspect its somewhere in between

That Xojo just didnt update as the OS API’s updated and now its come home to bite them

With MS there’s almost never a price to pay for NOT updating 76to the latest API because they do maintain backwards compatibility  
With Apple you have to move up, maybe not as rapidly as Apple does, to NOT have something break when they finally do make such changes
