# Customer support?

**URL:** <https://ifnotnil.com/t/customer-support/4709>\
**Category:** Other\
**Created:** [5 June 2026 22:57 UTC](https://ifnotnil.com/t/customer-support/4709 "2026-06-05T22:57:18Z")\
**Posts on this page:** 15\
**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:** [5 June 2026 22:57 UTC](https://ifnotnil.com/t/customer-support/4709/1 "2026-06-05T22:57:19Z")

</div>

> **[GraffitiSuite Web (62.1, 64) problems on Xojo 2026r1.2](https://forum.xojo.com/t/graffitisuite-web-62-1-64-problems-on-xojo-2026r1-2/88364)**
>
> Hi everyone, I’m trying to use my old versions of graffitiSuite r62.1 and r64.1 on Xojo2026r1.2, specifically I’m trying to use directly the versions of the sample project included in the two distributions, when I go to run the project I get...

🤦‍♂️

---

<div class="post-metadata">

**Author:** ![Torsten\_B](https://ifnotnil.com/letter_avatar_proxy/v4/letter/t/ecae2f/32.png) [@Torsten\_B](https://ifnotnil.com/u/Torsten_B)\
**Post date:** [6 June 2026 03:18 UTC](https://ifnotnil.com/t/customer-support/4709/2 "2026-06-06T03:18:38Z")

</div>

If we can’t break it today, we’ll break it tomorrow 😛

---

<div class="post-metadata">

**Author:** ![TomasJ](https://ifnotnil.com/user_avatar/ifnotnil.com/tomasj/32/4998_2.png) [@TomasJ](https://ifnotnil.com/u/TomasJ)\
**Post date:** [6 June 2026 06:42 UTC](https://ifnotnil.com/t/customer-support/4709/3 "2026-06-06T06:42:02Z")

</div>

Checked out the contract:\[1\]

> Without an active subscription, GraffitiSuite is under no obligation to provide live support, bug fixes, feature requests, access to previous releases, or access to the live support ticketing system.

I do not see any limitation to “current versions”. Only an active subscription is needed.  
And it looks like his Subscrption is still valid, at least for v64 which was released in October 2025.\[2\]

* * *

1. [GraffitiSuite - UI Shouldn't Be Hard - Support Policy](https://graffitisuite.com/legal/support-policy/) 

2. [Release 64](https://graffitisuite.com/enhance-your-apps-with-release-64/)

---

<div class="post-metadata">

**Author:** ![thorstenstueker](https://ifnotnil.com/letter_avatar_proxy/v4/letter/t/aca169/32.png) [@thorstenstueker](https://ifnotnil.com/u/thorstenstueker)\
**Post date:** [6 June 2026 10:51 UTC](https://ifnotnil.com/t/customer-support/4709/4 "2026-06-06T10:51:49Z")

</div>

What is most inteeresting: nobody, really nobody answered in XoJo Forum to this question. Hmmm…

---

<div class="post-metadata">

**Author:** ![thorstenstueker](https://ifnotnil.com/letter_avatar_proxy/v4/letter/t/aca169/32.png) [@thorstenstueker](https://ifnotnil.com/u/thorstenstueker)\
**Post date:** [6 June 2026 19:27 UTC](https://ifnotnil.com/t/customer-support/4709/5 "2026-06-06T19:27:47Z")

</div>

Oh. There was a reaction. Of Monkebread Software. That the Plugin is made always individually for the XoJo version and the only chance may be the switch to the newest version of the plugin to use it with the new XoJo version. That`s hard cause the plugin is wothless without maintenance contract. Much money to spend

---

<div class="post-metadata">

**Author:** ![TomasJ](https://ifnotnil.com/user_avatar/ifnotnil.com/tomasj/32/4998_2.png) [@TomasJ](https://ifnotnil.com/u/TomasJ)\
**Post date:** [6 June 2026 20:02 UTC](https://ifnotnil.com/t/customer-support/4709/6 "2026-06-06T20:02:56Z")

</div>

Seems like somebody just learned the Xojo Business-Case the hard way…

---

<div class="post-metadata">

**Author:** ![WhileNotNil](https://ifnotnil.com/letter_avatar_proxy/v4/letter/w/c57346/32.png) [@WhileNotNil](https://ifnotnil.com/u/WhileNotNil)\
**Post date:** [6 June 2026 21:05 UTC](https://ifnotnil.com/t/customer-support/4709/7 "2026-06-06T21:05:33Z")

</div>

Well, do you expect Anthony to fix a problem caused by a Xojo update in an older version of his suite?

The client could debug the JavaScript and try to fix it. Or get the newer version of the product.

---

<div class="post-metadata">

**Author:** ![thorstenstueker](https://ifnotnil.com/letter_avatar_proxy/v4/letter/t/aca169/32.png) [@thorstenstueker](https://ifnotnil.com/u/thorstenstueker)\
**Post date:** [6 June 2026 21:39 UTC](https://ifnotnil.com/t/customer-support/4709/8 "2026-06-06T21:39:44Z")

</div>

No, I do not. He is making it the right way. As he was one of the parties which decided for API 2 I would say no. You are fully right

---

<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:** [7 June 2026 03:46 UTC](https://ifnotnil.com/t/customer-support/4709/9 "2026-06-07T03:46:26Z")

</div>

> [@WhileNotNil](#):
>
> Well, do you expect Anthony to fix a problem caused by a Xojo update in an older version of his suite?
> 
> The client could debug the JavaScript and try to fix it. Or get the newer version of the product.

He COULD have had a look and pointed to a solution, even one that said “it is a bug that was fixed in the latest version” which MIGHT have resulted in a sale and a satisfied customer.

Instead he comes across as someone who only cares about getting money from his customers and has an annoyed customer who is unlikely to buy future updates.

Digging his own grave …

---

<div class="post-metadata">

**Author:** ![thorstenstueker](https://ifnotnil.com/letter_avatar_proxy/v4/letter/t/aca169/32.png) [@thorstenstueker](https://ifnotnil.com/u/thorstenstueker)\
**Post date:** [7 June 2026 04:58 UTC](https://ifnotnil.com/t/customer-support/4709/10 "2026-06-07T04:58:19Z")

</div>

At least he uses a really big excavator for his grave 🙂

---

<div class="post-metadata">

**Author:** ![Emile](https://ifnotnil.com/letter_avatar_proxy/v4/letter/e/58956e/32.png) [@Emile](https://ifnotnil.com/u/Emile)\
**Post date:** [7 June 2026 08:23 UTC](https://ifnotnil.com/t/customer-support/4709/11 "2026-06-07T08:23:13Z")

</div>

Remember:

a. We do not know what the bug is / we do not know how many times the bug cost to be removed

b. It is hard for Anthony to point the fault to Xojo (look at his status)

c. Unfortunately, it is like “I get a brand new Mac with a M6: my version of does not works anymore”

d. Check iOS requirements situation with Xojo

Also: I have no connection with any party involved.

OK, I do not like the situation, but a look to all parameters is better than what I read above. (most of)

---

<div class="post-metadata">

**Author:** ![Bad\_Wolf](https://ifnotnil.com/user_avatar/ifnotnil.com/bad_wolf/32/2308_2.png) [@Bad\_Wolf](https://ifnotnil.com/u/Bad_Wolf)\
**Post date:** [7 June 2026 08:57 UTC](https://ifnotnil.com/t/customer-support/4709/12 "2026-06-07T08:57:22Z")

</div>

Customer care is king. When customer care fails, the company that neglects it will ultimately fail too.

---

<div class="post-metadata">

**Author:** ![rgb](https://ifnotnil.com/letter_avatar_proxy/v4/letter/r/858c86/32.png) [@rgb](https://ifnotnil.com/u/rgb)\
**Post date:** [7 June 2026 15:24 UTC](https://ifnotnil.com/t/customer-support/4709/13 "2026-06-07T15:24:25Z")

</div>

True, Xojo are very y very small market. It’s hard to have new customers and easy to lost theirs.

---

<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:** [7 June 2026 15:38 UTC](https://ifnotnil.com/t/customer-support/4709/14 "2026-06-07T15:38:22Z")

</div>

Perfect example of not listening to your customers and suffering the results of not listening

Their forums used to be so active that not checking in hourly, or several times a day, meant you missed a bunch.  
Now ?  
A person could miss a week & not miss much

Personally I believe that is a reflection of their user base shrinking  
I _could_ be wrong but there are other signs that corroborate my suspicions

The # of posts on the “Pro” forums are way down  
Many years back there were several a month  
Then it dropped to several a quarter, then several a year  
Last year there were 5 or 6  
And so far this year, half way into the year, just one

There are other signs that also point to a shrinking user base

But users told them not to do several things along their last 7 or 8 years that they went and did without regard for how it would affect users & are seeing the results of not listening

Karma

---

<div class="post-metadata">

**Author:** ![dickey](https://ifnotnil.com/letter_avatar_proxy/v4/letter/d/958977/32.png) [@dickey](https://ifnotnil.com/u/dickey)\
**Post date:** [10 June 2026 07:26 UTC](https://ifnotnil.com/t/customer-support/4709/15 "2026-06-10T07:26:16Z")

</div>

In the interest of balance.

For the record, my business has received incredible customer service from Anthony in respect of GraffitiSuite, without exception.

Anthony’s continued support has been instrumental in keeping us moving forward.

On the Xojo Cloud front Jason Parsley provides amazing service as well.

GraffitiSuite has a fair policies.

> Try GraffitiSuite in your projects, for free! Debug as long as you want, and subscribe when you’re ready to build and distribute your applications!

Firstly, you don’t need an active subscription to test a version of GraffitiSuite against its supported version of Xojo.

Similar to Xojo, you can deploy with the last release of GraffitiSuite that was available to you whilst your annual subscription was current.

So, if GraffitiSuite Release 64 was the last version available to the OP prior to the lapse of his subscription, then the OP could continue to deploy apps GraffitiSuite 64 with any version of Xojo it supports.

Beyond that, an active subscription is generally required to deploy and receive support for current versions.

…and whilst nobody these days wants to pay for anything, Anthony’s support alone is worth the price of admission.

Kind regards, Andrew
