Skip to main content

StackJack 0.1.0.10721+4300bfe

StackJack 0.1.0.10721+4300bfe

This release fixes Xero connections that could not be validated or used, makes expired NinjaOne sign-ins easier to recognize and fix, and corrects the guidance shown when re-enabling an organization's connection.

Bug fixes

  • Xero connections that failed on every call now work. Some Xero Custom Connections had app-level permissions in their scope list that StackJack does not use. Those connections failed validation, and every Xero tool call returned an error. StackJack now leaves those permissions out when it signs in to Xero, so the affected connections validate and work. You don't need to change your Xero setup. Other scopes are unaffected.
  • Expired NinjaOne sign-ins are now reported as expired. NinjaOne ends a sign-in about 30 days after it is made. Previously, StackJack treated this as an unexpected error: the in-product message told you to re-enter credentials and pointed administrators to the organization's connection card, which was the wrong place. The connector-disabled email also gave "unexpected error" as the reason. StackJack now recognizes an expired NinjaOne sign-in. It shows guidance to re-authorize, and the disabled-connector email states the actual reason. When a team member's personal NinjaOne sign-in expires, that member receives the re-authorize email. Other connectors are unaffected.
  • Re-enable guidance for organization connections now names the right button. When re-enabling an organization's shared connection, such as HaloPSA, didn't succeed, the message could tell an owner to click "Re-authorize" under "Your personal sign-ins." The organization's connection card doesn't have that button. The message now directs you to the "Update credentials" (pencil) button on the organization's connection. This also applies to older accounts where the organization's connection is held under the account owner's sign-in. Guidance for personal connections is unchanged.
Bug Fix