iOS: composer does not auto-capitalize first letter of new sentence

Open Beginner friendly
#7,579 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
flutter
Domain
mobile

Research direction

Start by locating the Flutter TextField widgets used by the DM and channel message composers, then inspect their textCapitalization settings. Verify on iOS that the first word and the first letter after a period and space are capitalized in every message field.

Written by the indexing model from the issue text.

Description

Describe the bug

On iOS, the message composer does not auto-capitalize the first letter of a new sentence. The system keyboard stays in lowercase even after a period + space, so users have to manually toggle shift to start each sentence with a capital letter.

This happens in every message field (DMs and channel composers). Other iOS apps (Messages, Mail, Notes) auto-capitalize as expected.

Steps to reproduce

  1. Open Buzz on iPhone
  2. Start typing in the message composer: "hello there. "
  3. After typing the period and a space, the next letter is still lowercase: "hello there. how"
  4. Expected: "hello there. How"

Expected behavior

The keyboard's autocapitalization should follow iOS defaults for sentence input: capitalize the first letter of each sentence (and the very first word of the message). In Flutter terms, the composer TextFields should use textCapitalization: TextCapitalization.sentences (the Flutter default) rather than none.

Version and platform

  • Buzz version: iOS App Store build (latest, September 2026)
  • OS: iOS (iPhone)

Logs / additional context

None found searching the issue tracker for "autocapitalize", "capital letter", "textCapitalization" and similar terms — this appears unreported.

Dominant language
Rust
Stars
33.7k
Forks
4.4k
Avg merge
1d 21h
Merged PRs (30d)
239

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from block/buzz

All issues in block/buzz

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.