We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Этот сайт имеет ограниченную функциональность, пока мы проводим техническое обслуживание для улучшения его работы. Если какая-либо статья не решила вашу проблему и вы хотите задать вопрос, наше сообщество поддержки ждёт вас: @FirefoxSupport в Твиттере и /r/firefox на Reddit.

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

macOS Monterey refuses Thunderbird's authorization request for Contacts

  • 2 ответа
  • 1 имеет эту проблему
  • 9 просмотров
  • Последний ответ от Wayne Mery

more options

I've installed Thunderbird on a new MacBook with macOS Monterey, and the application is not requesting permission to access the Mac's Contacts. As a result, the macOS Address Book is empty and cannot read my contacts on my Mac.

This issue was first raised two years ago in an issue that was identified as a bug and was subsequently fixed and closed. It appears this bug has reappeared.

What should happen is Thunderbird should generate a system request to ask the user to allow it to access "Contacts". This request never appears. When I look at my Mac's System Preferences, under Security & Privacy -> Contacts, there is no entry for Thunderbird. I can't manually add this; the app has to generate the request.

Looking at my console, I found the following warning when I started Thunderbird:

Refusing authorization request for service kTCCServiceAddressBook and subject Sub:{org.mozilla.thunderbird}Resp:{<TCCDProcess: identifier=org.mozilla.thunderbird, pid=9492, auid=501, euid=501, binary_path=/Applications/Thunderbird.app/Contents/MacOS/thunderbird>} without NSContactsUsageDescription key

This message was reported in the bug referenced above. I believe something has probably changed in the latest version of macOS which is causing Thunderbird to incorrectly request access to Contacts from the system.

Should I reopen the bug? Create a new bug? Please advise.

Thunderbird 91.3.1 macOS Monterey (12.0.1) MacBook Pro 2021

I've installed Thunderbird on a new MacBook with macOS Monterey, and the application is not requesting permission to access the Mac's Contacts. As a result, the macOS Address Book is empty and cannot read my contacts on my Mac. This issue was [https://support.mozilla.org/en-US/questions/1269923 first raised two years ago] in an issue that was [https://bugzilla.mozilla.org/show_bug.cgi?id=1586617 identified as a bug] and was subsequently fixed and closed. It appears this bug has reappeared. What should happen is Thunderbird should generate a system request to ask the user to allow it to access "Contacts". This request never appears. When I look at my Mac's System Preferences, under Security & Privacy -> Contacts, there is no entry for Thunderbird. I can't manually add this; the app has to generate the request. Looking at my console, I found the following warning when I started Thunderbird: Refusing authorization request for service kTCCServiceAddressBook and subject Sub:{org.mozilla.thunderbird}Resp:{<TCCDProcess: identifier=org.mozilla.thunderbird, pid=9492, auid=501, euid=501, binary_path=/Applications/Thunderbird.app/Contents/MacOS/thunderbird>} without NSContactsUsageDescription key This message was reported in the bug referenced above. I believe something has probably changed in the latest version of macOS which is causing Thunderbird to incorrectly request access to Contacts from the system. Should I reopen the bug? Create a new bug? Please advise. Thunderbird 91.3.1 macOS Monterey (12.0.1) MacBook Pro 2021

Все ответы (2)

more options

It seems a fix might not happen soon.

Workaround https://bugzilla.mozilla.org/show_bug.cgi?id=1720257#c25

more options

This should be fixed by https://bugzilla.mozilla.org/show_bug.cgi?id=1720257 in one of the next updates of version 102 (but not 102.10.0)