Icon is above Apple icon in top navigation bar

[AndreasGJ]

Checks

• [X] I have searched github.com/withfig/fig/issues and there are no duplicates of my issue
• [X] I have run fig doctor in the affected terminal session
• [X] I have run fig restart and replicated the issue again

Operating system

macOS 14.0.0 (23A344)

Expected behaviour

Being able to click on my main apple top menu.

Actual behaviour

Fig icon is above it and therefor I can't click it.

Steps to reproduce

Install Fig app with the new macOS 14.0

Environment

fig-details:
  - 2.17.0
hardware-info:
  - model: 
  - model-id: 
  - chip-id: Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
  - cores: 4
  - mem: 16.00 GB
os-info:
  - macOS 14.0.0 (23A344)
environment:
  - shell: /bin/zsh
  - terminal: iterm
  - cwd: /Users/andreasgh
  - exe-path: /usr/local/bin/fig
  - install-method: unknown
  - env-vars:
    - FIGTERM_SESSION_ID: 859e14a5-131c-4368-9815-8fe5f8565ab7
    - FIG_SET_PARENT_CHECK: 1
    - FIG_TERM: 2.17.0
    - PATH: /usr/local/opt/[email protected]/sbin:/usr/local/opt/[email protected]/bin:/Users/andreasgh/.pyenv/shims:/usr/local/sbin:/Users/andreasgh/.nvm/versions/node/v16.14.2/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/Users/andreasgh/.fig/bin:/Users/andreasgh/.local/bin:/Users/andreasgh/.composer/vendor/bin
    - SHELL: /bin/zsh
    - TERM: xterm-256color
    - __CFBundleIdentifier: com.googlecode.iterm2
    - FIG_PID: 39574
    - FIG_SET_PARENT: 859e14a5-131c-4368-9815-8fe5f8565ab7

[andreekeberg]

This happened to me as well right after I upgraded macOS to Sonoma, so it's definitely related to Sonoma.

The correct, black icon, shows in the right place, but a white version is shown on top on the Apple icon.

I see that this has been mentioned in both #2754 and #2418 which have both been closed even though this is still very much an issue.

[andreekeberg]

@mschrage When you have been trying to reproduce this, were you using Sonoma as well?