Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Settings API not honoring longScanForcingEnabled #1217

Open
davidgyoung opened this issue Dec 19, 2024 · 0 comments · May be fixed by #1218
Open

New Settings API not honoring longScanForcingEnabled #1217

davidgyoung opened this issue Dec 19, 2024 · 0 comments · May be fixed by #1218

Comments

@davidgyoung
Copy link
Member

Expected behavior

The new settings API is supposed to allow you to use the following rather than inserting a value in the deprecated means of setting the value AndoirdManifest.xml

val settings = Settings(
            longScanForcingEnabled = true
)
beaconManager.repalaceSettings(settings)

Actual behavior

The above code has no effect, meaning that the deprecated means of setting this in the AndroidManifest.xml is still required until the bug is fixed. A similar problem exists with two other minor settings with settings.getRssiFilterImplClass()

Steps to reproduce this behavior

Modify the reference app to add the above settings with a foreground service and scan periods with a 100% duty cycle, then let the scan run for over 30 minutes. Note a warning in the log that scans will be stopped.

Mobile device model and OS version

Andorid 7.1+

Android Beacon Library version

2.21.0-beta2+

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 a pull request may close this issue.

1 participant