Skip to content

fix(share): render the share extension in Avenir - #1044

Merged
bmc08gt merged 1 commit into
mainfrom
fix/share-extension-fonts
Oct 11, 2026
Merged

bmc08gt merged 1 commit into
mainfrom
fix/share-extension-fonts

Conversation

@bmc08gt

@bmc08gt bmc08gt commented Oct 11, 2026

Copy link
Copy Markdown
Collaborator

The share extension's Send to screen used system text styles (.headline, .subheadline, .footnote), so it rendered in San Francisco instead of the app's Avenir.

  • Each element now uses the token ShareToChatsSheet uses for the same element: .appBarButton for the title, .appTextSmall for section headers, 17pt Demi for chat names, .appTextMessage for the search and message fields, 17pt Medium for Send.
  • ShareViewController registers Avenir Medium and Demi at launch. The styles above stay within those two faces, so Regular isn't loaded into the extension's memory budget.
  • FontBook.registerNotificationFonts() is renamed registerExtensionFonts(), since the notification and share extensions both call it now.

The Send to screen used system text styles (.headline, .subheadline,
.footnote), so it rendered in San Francisco while the rest of the app
uses Avenir. Each element now takes the token ShareToChatsSheet uses for
the same element, and the extension registers Avenir Medium and Demi at
launch.

registerNotificationFonts becomes registerExtensionFonts, since both
extensions now call it.
@bmc08gt bmc08gt self-assigned this Oct 11, 2026
@bmc08gt
bmc08gt merged commit d4c366b into main Oct 11, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant