Zach 818f514702 The first issue was that the toggle switch states weren't being initialized when settings were refreshed from the device. The code would correctly update the interval values themselves, but failed to set the corresponding boolean flags that control whether the toggles appear as "on" or "off". This meant that if you refreshed settings from a device that had advertisements disabled (with an interval of zero), the toggles would incorrectly show as enabled even though the device was actually broadcasting no advertisements. We fixed this by adding two lines that explicitly set _advertEnable = _advertInterval > 0 and _floodAdvertEnable = _floodAdvertInterval > 0 after parsing the interval values from device responses. ...

The second critical bug was in the validation logic that checks whether responses from the device contain valid data. The validator was rejecting any interval values of zero because it checked interval > 0, but zero is now a meaningful and valid value that indicates advertisements are disabled. Without this fix, any time a device reported back that advertisements were disabled, the app would silently discard that information as invalid, leaving the UI out of sync with reality. We changed the validation to use interval >= 0 instead and updated the comment to explicitly document that zero means disabled.

The third fix was a minor code style issue where a single-line if statement was missing braces, causing a linter warning. This doesn't affect functionality but ensures the code meets project standards.

2026-02-01 17:08:53 -07:00

..

connector

fix commit

2026-02-01 16:57:17 -07:00

helpers

feat: optimize reaction message format to reduce airtime

2026-01-28 23:21:04 -07:00

l10n

fix commit

2026-02-01 16:57:17 -07:00

models

Refactor contact handling and enhance UI with new advert options and localized strings

2026-01-28 11:04:34 -08:00

screens

The first issue was that the toggle switch states weren't being initialized when settings were refreshed from the device. The code would correctly update the interval values themselves, but failed to set the corresponding boolean flags that control whether the toggles appear as "on" or "off". This meant that if you refreshed settings from a device that had advertisements disabled (with an interval of zero), the toggles would incorrectly show as enabled even though the device was actually broadcasting no advertisements. We fixed this by adding two lines that explicitly set _advertEnable = _advertInterval > 0 and _floodAdvertEnable = _floodAdvertInterval > 0 after parsing the interval values from device responses.

2026-02-01 17:08:53 -07:00

services

Merge origin/main into pr-106

2026-01-28 22:22:43 -07:00

storage

feat: Add community management features with QR code scanning

2026-01-19 20:56:07 -07:00

utils

Add localization support and translation script

2026-01-11 17:13:50 -07:00

widgets

feat: optimize reaction message format to reduce airtime

2026-01-28 23:21:04 -07:00

main.dart

Fix issues flagged by flutter analyze

2026-01-17 11:00:34 -05:00