Shiftブラウザ not working: what to check, in order

The frustrating part of troubleshooting this particular app is not the fault itself. It is that the fix found online frequently describes a screen that does not exist on the machine in front of you. A setting sits in a different menu, a button named in the instructions is missing, two pages on the same site quote different prices. Most of that is not a bug and not bad documentation. It is a version boundary, and checking which side of it you are on takes about ten seconds.

What follows is ordered by what narrows the problem fastest, not by symptom. Working top down means each step eliminates a whole class of causes rather than one specific complaint.

Check the version before anything else

Shift currently exists as two builds. The older v9 and a rebuilt Shift browser are both installed on machines right now, because the replacement is rolling out to existing users over a period of months rather than all at once.

To find out which one is running: launch the app, open the Shift menu in the macOS menu bar, and choose About Shift. A version number that begins with 9 is the older build.

The differences are structural, not cosmetic. In the older build, each Space had to be associated with an email account. The current build removes that requirement and allows apps to be placed anywhere in the layout rather than in fixed regions. Bars, apps, and controls can be dragged, layouts can start from a template, and eight color themes exist in light and dark variants.

That explains a whole category of reported problems. A missing field for attaching an email address to a Space is not a fault, it is a removed requirement. Being unable to drag an app to an arbitrary position is not a fault either, it means the older build is installed.

The interface changed overnight

A layout that looks different one morning usually means the rollout arrived. During that transition, Spaces, apps, and bookmarks are carried across automatically.

The exception is anyone who installed the new version manually before the rollout reached them. A manual install opens empty, with nothing migrated, which reads exactly like a total loss of settings. Signing in with the email address already attached to the subscription keeps paid features intact even in that case, and it is the one step worth doing immediately after an early install.

Before concluding that data is gone, it is worth checking which of those two situations applies. One resolves itself, the other needs a rebuild.

Settings will not open

This one has a specific cause and a specific keystroke.

Because the current build allows the interface to be assembled by hand, the Quick Settings icon can be removed from the layout during customization. Removing it removes the entrance to every setting, which makes the application look locked.

If you removed the Quick Settings icon from your Shift setup, you can access Quick Settings to revert this change with a keyboard shortcut. Source: tryshift.com

On a Mac the shortcut is Command plus comma. On Windows it is Ctrl plus comma. Once the panel is open, Customize Layout puts the button back where it belongs.

Worth noting before assuming it is gone: with a template or a custom layout in use, the Quick Settings icon is not necessarily in the default top right position. Absence from that corner is not proof of anything.

It launches by itself, or it never updates

Both of these live in the same place, and neither needs macOS system settings to be touched first.

For an application that opens on login or reappears after the machine wakes, open Quick Settings, then Advanced Settings at the bottom of the drawer, then On Startup in the left panel. Two toggles sit there, Open on wake and Open on login, and the symptom identifies which one applies. Wake behavior and login behavior are separate settings, so turning off one does not affect the other.

For updates, the same Advanced Settings panel has About Shift. If an update is pending, a Relaunch button appears next to the version number and applies it.

One caveat changes the interpretation of a missing update. No further major product updates are planned for v9. On that build, waiting for a new feature to arrive through the updater will not produce one, because the feature belongs to the rebuilt browser. The choice at that point is to wait for the rollout or to install the new version manually and rebuild.

It is slow, or it will not run at all

Before extensions and caches, check the documented requirements, because a machine below the line produces symptoms that look like performance problems.

• macOS 11 Big Sur or newer is required. The requirement comes from Chromium underneath, so it tracks the Chrome system requirements
• At least 8GB of RAM is the stated recommendation for smooth operation, and that figure assumes an ordinary workload rather than twenty apps held open in one layout
• Supported platforms are Windows 10 and 11 and Mac. There is no mobile version

The macOS version appears under About This Mac in the Apple menu. If the requirements are met and it is still heavy, count the apps pinned into the layout. Each one is a live view, and things opened twice a month do not need a permanent position. Removing them is usually faster than any other intervention.

Visual glitches, as opposed to slowness, tend to follow a manual layout change. A hand built arrangement can overlap at narrower window widths in ways a template will not. Applying a template temporarily is a clean way to tell whether the layout or the application is at fault.

Downloads stall, or search results come from somewhere unexpected

A download that pauses or triggers a warning may be working as designed. Files are screened against a file reputation service before they are written to disk, so that dangerous files never reach the desktop. The file itself is not transmitted or stored during that check, and the local antivirus software still runs its own scan afterward. Internally distributed files sometimes trip this first layer.

A warning before a page loads comes from URL checking. Part of the address is compared against a list of known scam and dangerous sites, and a match produces a warning before anything renders. Browsing history is not recorded as part of that process.

Search results arriving from an unexpected engine is a settings question rather than a hijack. Quick Settings, then Advanced Settings, then Search Engine in the left panel, then Change next to the current entry. The available options are Google, Bing, Yahoo, and StartPage, and the choice is confirmed with Set as Default.

For extensions that refuse to work, the documented scope is nearly everything in the Chrome extension library. When a specific one fails inside that scope, the likely cause is the extension checking which browser it is running in, not a missing capability.

Two machines that never match, and notifications that never arrive

Different setups on a work machine and a home machine usually means sync was never enabled. The current build can be used without creating an account at all, which is convenient at first and means settings stay local until someone signs in.

Turning it on: Quick Settings, then Advanced Settings, then the Sync Shift section, then Turn on Sync. Layout, Spaces, apps, bookmarks, and history then follow the account. A subscription covers one account, and that one account signed in on several machines is the supported arrangement.

Missing notifications have two layers. The web app itself has to have notification permission, and macOS has to be allowing the application through in System Settings. A Focus mode active during the day suppresses delivery regardless of both. Turning Focus off and reproducing the problem separates the two layers in one attempt.

Notifications that arrive without identifying the account are a different matter and no setting fixes them. The payload carries the service name and nothing more. When that causes constant checking, the thing to change is how the workspaces are divided, not a preference.

Payments fail, or charges keep arriving

Billing is where symptom and cause sit furthest apart.

Payments run through Stripe, and accepted cards are Visa, Mastercard, and American Express. Debit cards, gift cards, and PayPal are not accepted, so a failure with any of those is the documented behavior rather than a fault. When the card type is correct and the charge still fails, the next suspect is the bank, since some banks block recurring charges until explicitly authorized. Trying a different card is the documented next step.

Charges that continue after what felt like a cancellation almost always trace back to uninstalling instead of cancelling. Removing the application does not end the subscription. Cancellation happens by signing in to the account portal and using the Subscription tab, after which paid features remain available until the next renewal date and the account then moves to the free plan. Renewal is annual, and the renewal date is visible in the same tab, which matters because the refund window is 14 days from a purchase or a renewal charge.

When none of it works, the exits are separate

Three things people tend to ask for together are handled through three different routes, and combining them into one request slows all three down.

Reporting a defect goes through a support ticket. The support side collects the details needed and passes the report to the development team, so a ticket with the version number, the platform, and the steps that reproduce it moves faster than a description of the symptom alone.

Cancelling a subscription is self service through the account portal, under the Subscription tab. On the current build, support can also do it on request. Nothing about cancelling touches the data.

Deleting an account and its data requires a separate support request. Processing takes time, and confirmation arrives once it completes. This is the only one of the three that actually removes anything.

Removing the application on a Mac is a fourth action again: open Finder, go to the Applications folder, move Shift to the Trash, and empty it. That ends nothing financially and deletes nothing stored server side, which is precisely why the previous two steps exist as their own procedures.

Knowing all four before starting is what keeps a bad afternoon from turning into a bad quarter. An uninstall performed in frustration leaves a live subscription behind, and the renewal arrives months later with no application on the machine to explain it.

What to change first

Confirm the version before touching any setting, because that single check decides whether the instructions being followed describe the screen in front of you. After that, work outward in this order: the entrance to settings, startup behavior, system requirements, then billing. If the underlying problem turns out to be that one workspace going wrong takes the whole setup with it, the boundary worth examining is how the workspaces are separated in the first place, which is covered in SpaceDeck, with the supported services listed under Supported apps.