Unite not working: what to check, in order

A Unite app that suddenly misbehaves invites the worst debugging habit there is: opening the settings pane and toggling things. The published release history for this app suggests a better order. Most reported symptoms have been fixed in a version rather than in a setting, which means the fastest path runs through updates before it runs through configuration. What follows is that order, with the evidence for why each step sits where it does.

Step one: reproduce it in Safari

Before touching anything, open the same URL in Safari. If the symptom appears there too, the cause is on the site, in the account state, or on the network, and no amount of app configuration will move it.

This test works because Unite apps are built on WebKit rather than on a bundled Chromium. The comparison page describes the engine as a custom browser built specifically for site-specific browsers and powered by Apple's open source WebKit 2. Same rendering foundation, same rendering bugs. When a site ships a change that breaks layout, Safari breaks the same way. If Safari is fine and only the app is broken, the problem lives in the wrapper, and everything below applies.

Step two: update the tool and the apps it built

This is where the largest share of reports land. Unite Pro updates through Sparkle, with a manual check available from the Unite menu.

The part that gets missed: updating the tool does not automatically mean your existing apps are current, if the relevant preference was ever turned off. There is a setting under Preferences, General called "Automatically update created apps," enabled by default. With it off, apps stay at whatever version they were built against until they are edited and saved again in Unite Pro.

The changelog shows how often the fix has lived here:

• 1.3, April 23, 2026: improved compatibility with Cloudflare and Akamai security prompts
• 1.5, June 18, 2026: fixed NotebookLM modules failing to load, fixed fullscreen playback in YouTube playlists and Netflix, updated the built-in user agents
• 1.6, July 26, 2026: fixed background inefficiencies that slowed typing and response streaming on ChatGPT-style sites
• 1.7, August 9, 2026: fixed an intermittent crash when closing tabs
• 1.8, August 30, 2026: fixed shortcuts on non-Latin keyboard layouts and userscripts having their straight quotes rewritten

Read that list again with a symptom in mind. "One specific site behaves oddly" has repeatedly been a version problem, not a settings problem.

Step three: rebuild the app

If updating did not resolve it, edit the app in Unite Pro and save it again. That regenerates the app bundle against the current version.

This step earns its place right after updates because of what happens around a macOS upgrade. Support documentation describes exactly this sequence: after an OS upgrade, check for a Unite Pro update first, then edit and save the affected app to rebuild it against the current version. Apps built against an older OS can be the only thing left behind when window behavior or rendering changes underneath them.

When pages stall at login or refuse to load

Endless verification spinners, challenge pages that never clear, requests treated as automated traffic. This family points at the user agent.

Unite exposes default user agents plus automatic switching based on site or path, and this area has been revised repeatedly. Version 1.5 updated the built-in user agents and fixed a bug where a selected user agent preset could reset unexpectedly after a Safari or macOS update. That second one is worth noting: a preset that was configured correctly months ago may no longer be the one in effect, so check what is currently selected rather than assuming.

Security challenge screens have their own fix history, in 1.3. For a site that still refuses to cooperate, forwarding just that domain to the default browser and completing authentication there is a workable arrangement rather than a defeat.

When the keyboard stops behaving

For anyone typing in a language that uses an input method, this is the most common category, and the changelog is unusually specific about it.

Version 1.2.1, April 6, 2026, improved keyboard shortcut routing for Japanese and Chinese input and fixed app-level shortcuts intruding on web text editors such as Google Docs. The same release fixed Cmd+L failing to focus the URL bar and Cmd+F failing to refocus the Find panel. Version 1.4, May 10, 2026, fixed the Shift key being captured by the shortcut listener and therefore failing on certain sites. Version 1.7 fixed Cmd+Shift+[ and Cmd+Shift+] skipping every other tab. Version 1.8 fixed non-Latin keyboard layouts and common editing shortcuts firing twice.

So the triage is short:

• Characters vanishing mid-composition, or a paste landing twice, points at the version
• A shortcut that fails only inside one site points at a collision between the app binding and the site binding
• Collisions are resolvable: the shortcut manager lets every binding be searched and rebound, so remove the one that clashes

What does not work well here is guessing at settings. Version drift explains most of it.

When badges and permissions disagree with reality

A Dock count that does not match the inbox is often not a defect. The documentation is explicit about the mechanism:

Badges reflect the unread count as shown by the website itself. Source: help.bzgapps.com

If the site displays "99+", the Dock shows 99. If the site only refreshes its count once the page is opened, the badge cannot move any earlier. Badge support is organized into four categories, covering email services like Gmail and Outlook, chat services like Slack and Discord, work tools like Linear and Jira, and AI services.

Genuine defects in this area do exist and have been fixed. Version 1.0.2, March 16, 2026, corrected Gmail badges showing draft counts instead of inbox counts, and tab favicons getting stuck on an old notification number. The same release fixed camera, microphone, and location permissions failing to persist between sessions, which is the usual explanation when a meeting or a microphone stops working for no apparent reason.

When links open somewhere unexpected

Link forwarding decides, per URL, whether something opens in the app, gets ignored, goes to another browser, or goes to another Unite app. Two version-specific traps live here.

First, wildcards. Version 1.6 fixed whitelist patterns containing wildcards, such as a local address range or a domain pattern, failing to match as expected. A rule that looks correct may simply not have been matching before that release.

Second, the default browser. The same release fixed "Forward to default browser" getting stuck on whichever browser was default at the moment the setting was first enabled, rather than following the current macOS default. Anyone who switched browsers and found links still going to the old one was hitting exactly this.

Links that hand off to native apps through custom URL schemes were added in 1.1 and refined in 1.5, which introduced clearer confirmation behavior, remembered choices, and protection against repeated background launch attempts.

When tabs and windows behave strangely

A separate family of symptoms has nothing to do with the site being displayed: tabs that reappear after being closed, a click on the Dock icon that produces an empty page, a popup that never shows up. These are wrapper behaviors, and they have their own fix history.

Version 1.2, March 30, 2026, fixed a Dock icon click unexpectedly opening a blank tab, and fixed a stray tab opening at launch in certain menu bar configurations. Version 1.6 fixed tabs opened by a site through "open in new tab" links becoming unresponsive or stuck, and fixed launching an app from a link also opening an extra home page tab, adding a setting to suppress that. Version 1.7 fixed startup tabs being duplicated after relaunch and tabs that were deliberately closed coming back.

The reason to treat this as its own category is that none of it is fixable from the site side or by clearing data. If closed tabs keep returning, checking the version number is a faster move than rebuilding the app or reconfiguring startup pages.

Downloads fall into the same bucket. Version 1.8 changed the save dialog so it remembers the last folder chosen, and 1.3 added an option to reset the download location back to the default path along with a fix for a download banner that would not dismiss. A download prompt that keeps landing in the wrong folder is a known behavior with a known release attached to it.

When it will not start rather than will not work

If the symptom is an activation dialog rather than a broken page, the cause is licensing. An error stating that the license code has already been utilized means the key is still bound to another machine that was never deactivated. The published resolution is to deactivate on the original Mac from the Unite menu, then register again. If that machine is gone, contacting support with the purchase email releases the activation.

Subscription users hit a different wall. Apps created through a Setapp-activated copy require Unite to be opened at least once every 30 days to confirm the subscription is still active. Past that, created apps show a verification dialog. Opening Unite Pro resolves it immediately. Since this arrives without warning for anyone who builds apps and never reopens the tool, it is worth recognizing on sight.

Symptoms that only appear right after migrating

Apps carried over from Unite 6 have their own short list. Migration preserves the URL, app name, icon, display mode, browsing data, saved passwords, bookmarks, history, and user scripts and styles. Two things do not survive. Legacy Dock Slices configurations were replaced by the new Dock Monitor and have to be set up fresh, and Compact mode no longer exists, so apps using it are migrated to Normal mode. Some advanced settings also need reconfiguring in the new settings interface.

If the migration sheet lists nothing at all, that is a discovery problem rather than a failure. The scanner checks the Applications folder and configured save locations, so apps sitting in a subfolder or on an external drive have to be dragged into the sheet manually. Migration itself requires an active license, and so does exporting a backup beforehand.

What to change first

Work the order rather than the settings pane: reproduce in Safari, update both the tool and the created apps, rebuild the app, then isolate by layer. Before contacting anyone, write down three things, the Unite Pro version, the version the app was built against, and the exact URL, because those three turn a vague report into a changelog lookup. If rebuilding apps after every browser or OS change is the part that keeps costing time, compare how different approaches handle that: the Features page and the Supported services list show what a tool like Kagemusha repairs on its own versus what it leaves to you.