[BUG] FluidMeet promo notification appearing when disabled
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos, swift
- Domain
- desktop-dev
Research direction
The report says the FluidMeet promo notification fires even though the setting is off, so start by finding where that promo notification is scheduled and where the FluidMeet-enabled preference is stored (likely a UserDefaults key) and read how they interact at launch. Check whether the disable check is missing on the scheduling path or whether the preference is being reset when the app starts. Done when launching the app and starting a Zoom meeting with FluidMeet disabled produces no promo notification, and the setting survives a relaunch. The payload names no files, so expect to search the Swift sources for the notification and preference strings first.
Written by the indexing model from the issue text.
Description
Describe the bug
I have FluidMeet disabled and am still seeing desktop notifications to setup recording. It seems like it reenabled itself again.
This app is rapidly getting worse and worse, It's quite frustrating.
Reproduction steps
- Open Fluidvoice
- Start a Zoom meeting
Expected behavior
See notification randomly during the meeting
Actual behavior
Notification appears
App Version
Version 1.6.12 (30)
macOS Version
macOS 15.8.1 (24H32)
Architecture
Apple Silicon
Logs or crash report
Screenshots or screen recording
No response
- Dominant language
- Swift
- Stars
- 11.9k
- Forks
- 863
- Avg merge
- 2d 54m
- Merged PRs (30d)
- 42
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from altic-dev/FluidVoice
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
altic-dev/FluidVoice#1284 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
altic-dev/FluidVoice#1280 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
altic-dev/FluidVoice#1191 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 45/100
altic-dev/FluidVoice#1285 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 Half a day Newbie friendliness 38/100
altic-dev/FluidVoice#1283 ·
Maintainers usually reply within 1 day
All issues in altic-dev/FluidVoice
Similar issues
-
area: agents area: layout S3: minor
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
manaflow-ai/cmux#34277 · 1 comment ·
Maintainers usually reply within 1 day
-
priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
thunderbird/thunderbird-ios#599 ·
Maintainers usually reply within 1 day
-
bug core p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
RunanywhereAI/runanywhere-sdks#1258 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
googleapis/google-cloud-swift#1581 ·
Maintainers usually reply within 1 day