[Bug]: onedrive always in hidden section

[dginige-spec]

Search for Similar Reports

• I have searched existing issues for similar reports

Description

Hi, I have noticed that the onedrive app always goes to the hidden section and does not stay in the visible area. I have rebooted and it always goes back to the hidden area.

Steps to Reproduce

move onedrive to visible and then reboot and it will move it back to hidden.

App Version

1.2.0

macOS Version

26.5

Monitor Setup

Multi-monitor Setup

Additional Information

No response

[github-actions]

👋 Hi @dginige-spec! Thanks for the report.

This sounds like a known issue where some apps (like OneDrive) don't persistently save their menu bar icon position, causing macOS to repeatedly treat the icon as "new" and place it in the always-hidden section. This was addressed in a recent fix — see FREQUENT_ISSUES.md for context.

To help us investigate whether this is still occurring on the latest version, could you please provide:

• Thaw version (visible in the Thaw menu or About screen)
• macOS version
• Steps to reproduce — e.g., does OneDrive return to the hidden section after every reboot, or on every launch of OneDrive?
• Expected vs. actual behaviour

Workaround in the meantime: Option + click the Thaw icon to reveal the always-hidden section, then ⌘ + drag OneDrive's icon to your preferred section.

Thanks! 🙏

Note

🔒 Integrity filter blocked 37 items

The following items were blocked because they don't meet the GitHub integrity level.

• #607 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #607 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #600 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #366 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #389 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #261 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #462 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #62 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #286 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #224 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #120 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #138 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #456 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #605 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #575 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #559 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 21 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Issue Triage for issue #607 · ● 1.8M · ◷

[diazdesandi]

@dginige-spec Could you please update to the latest beta and report back? Thank you.

[IamWJC]

Hello, I can confirm this issue. Mine always appears in the "Hidden" section. I suspect it's in the "Always Hidden" section, but I have that turned off, so I can't fully confirm that.

I'm at work at the moment, so I can't reboot to confirm that, but that's what I suspect.

Thaw version: 1.2.0 (30)
macOS version: 26.5 (25F71)
Steps to reproduce:

• Have OneDrive installed and set to start with system startup
• Make sure you have moved OneDrive into the Visible section
• Reboot your computer, login, and wait for everything to startup
• Notice that OneDrive is not showing in your menu bar
• Because I have the "always hidden" section disabled, I suspect it's going there, but if I open OneDrive again (I use spotlight for this), it shows then in the "Hidden" section and I can move it back to Visible

Expected vs. actual behavior:

• Expected: OneDrive would show in my menu bar
• Actual: It's not in OneDrive nor in the "Hidden" section when I expand that out until I run the OneDrive application again

[diazdesandi]

@IamWJC thanks for the details, can you switch to the beta channel and update to 2.0.0 beta 12 and report back?

[dginige-spec]

i removed a few comments about updating. found beta 12 and will update and check the status

[dginige-spec]

after the beta installed i added onedrive and then rebooted

after the reboot one of my one drive was showing but it was in the hidden section showing where it shouldnt.

these are the other hidden items

so - no it does not look like it is fully working.

[SnoElement]

Seeing the same behaviour on macOS 26.5, Thaw 1.2.0. OneDrive consistently ends up in the "always hidden" section regardless of where it's placed.

Found some relevant evidence in the unified system log. OneDrive's own logs show it periodically reconnects its status item scene (same UUID, explicitly logged as "Reconnecting scene") — likely triggered by sync state changes or wake from sleep. macOS handles this fine and the icon position is preserved on the stock menu bar. However, Thaw appears to hold a reference to the previous scene handle, and when that goes stale it can't find the scene to update:

[FrontBoardServices] [<scene>-Replicant[N]-Aux[1]-NSStatusItemView] No matching scene to invalidate for this identity.
[BaseBoard] [BSBlockSentinel:FBSWorkspaceScenesClient] failed!
[FrontBoardServices] [<scene>-Replicant[N]] Sending action(s): NSStatusItemClearAutosaveStateAction

The NSStatusItemClearAutosaveStateAction appears to be Thaw's fallback on a stale scene reference — and it resets the saved position. In one session this became a retry loop (Replicant[71] through [79] over ~4 seconds), with the position being cleared on each attempt, coinciding with a high memory warning (519–525MB).

The end result is the icon ends up in "always hidden" rather than just reverting to "hidden". Since macOS itself tracks the reconnection correctly, this looks like Thaw needs to handle scene reconnection events and reattach to the new scene handle rather than falling back to clearing autosave state.

[nightah]

after the beta installed i added onedrive and then rebooted

after the reboot one of my one drive was showing but it was in the hidden section showing where it shouldnt.

these are the other hidden items

so - no it does not look like it is fully working.

Can you provide a dump of the command defaults read com.stonerl.Thaw?

Also, where is your "New Items" indicator (a screenshot of your layout pane would help us visualise), is it perhaps in the hidden section and also perhaps where the second OneDrive icon is appearing?