[BUG] FluidMeet: Google Meet browser calls not detected after Meet moved rooms to /meet/<code>

Closed Beginner friendly
  • Is something wrong?
#1,264 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

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
swift
Domain
desktop

Research direction

Start at MeetingInCallURLMatcher.matchesGoogleMeetPath and check how it validates the Google Meet room-code path. Accept the optional leading meet/ segment while preserving recognition of the existing URL form; done means FluidMeet recognizes calls at both URLs and offers to record.

Written by the indexing model from the issue text.

Description

Describe the bug

FluidMeet no longer detects Google Meet calls in the browser. Google Meet now moves you from meet.google.com/abc-defg-hij to meet.google.com/meet/abc-defg-hij when you join. FluidMeet only treats the first form as a call, so it reads the address, decides it is not a meeting, and never offers to record.

The room code check in MeetingInCallURLMatcher.matchesGoogleMeetPath expects the whole path to be the code. With the /meet/ prefix, the path becomes meet/abc-defg-hij, which fails the length check. The same code is still on the main branch.

Accepting an optional leading meet/ segment before the room code should fix it.

Reproduction steps
  1. In FluidMeet settings, turn on meeting auto-detection and browser meetings.
  2. Open a Google Meet link such as https://meet.google.com/abc-defg-hij.
  3. Join the call. The address changes to https://meet.google.com/meet/abc-defg-hij.
  4. Wait while the call runs.
Expected behavior

FluidMeet recognizes the call and offers to record it, as it does for Zoom.

Actual behavior

No prompt appears. The log shows the address being read every two seconds and rejected each time, even though the mic is active. See the log below.

App Version

1.6.13-beta.1

macOS Version

macOS 27.2

Architecture

Apple Silicon

Logs or crash report
[15:30:07.274] [INFO] [MeetingAutoDetector] record-armed bundle=com.google.Chrome.app.kjgfgldnnfoeklkmfkjfagphfepbbdan
[15:30:20.213] [INFO] [MeetingAutoDetector] audio-evidence-begin path=device bundle=com.google.Chrome.app.kjgfgldnnfoeklkmfkjfagphfepbbdan
[15:30:21.860] [INFO] [MeetingAutoDetector] browser-url-read outcome=found host=other in-call=false bundle=com.google.Chrome.app.kjgfgldnnfoeklkmfkjfagphfepbbdan
[15:30:23.999] [INFO] [MeetingAutoDetector] browser-url-read outcome=found host=other in-call=false bundle=com.google.Chrome.app.kjgfgldnnfoeklkmfkjfagphfepbbdan
... (repeats until the call ends)
[15:31:10.210] [INFO] [MeetingAutoDetector] audio-evidence-end path=device bundle=com.google.Chrome.app.kjgfgldnnfoeklkmfkjfagphfepbbdan

Browser history shows the redirect from the plain room address to the /meet/ address starting around October 21, 2026. In about three weeks of logs, auto-detection has started for Zoom but never for a browser Google Meet call.

This may also be related to #1223, where a Google Meet call in Chrome was not matched to a meeting app.

Dominant language
Swift
Stars
11.9k
Forks
863
Avg merge
2d 4h
Merged PRs (30d)
43

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 altic-dev/FluidVoice

All issues in altic-dev/FluidVoice

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.