Problem with repeated Distance Outputs

[sparkweaver]

When using the app to measure walking distance, the console prints multiple output lines if the measurement action is stopped and started repeatedly. This can lead to performance and device battery problems.

Investigation

• Tested distance calculation methods: All parts that are directly related to distance measuring do not seem to be the cause of the problem.
• Code Review: The implemented Geolocation code has a bit of refactoring from the Microsoft document version but none that would be cause for the problem.

Next Step

• Further investigate GeolocationService.
• Read Request location permissions in: https://developer.android.com/develop/sensors-and-location/location/permissions to ensure that the incorporation of the geolocation is correct.
• Consider using another method of retrieving the location.

[sparkweaver]

I will look at this before the first deployment. I don't want to have issues with memory leaks when running it on my phone.

Investigate the GeolocationService code

Changes

• Introduced Flag: Implemented a control, using the isListeningToLocation to prevent overlap or execute concurrently, leading to possible unpredictable behavior. Thus ensuring state consistency.
• Event Trigger Check Method: Added a method to systematically check each trigger of the LocationChanged event. This was an attempt to identify if the frequent triggering was due to an issue with the emulator setup or a bug within the code itself.

Test and Analysis

• The output logs showed one-to-one correspondence between event triggers and the expected handling. This makes me believe that the subscription to the Locationchanged event is managed correctly.

Next Step

• Documentation Review: I will read the documentation on the emulator and settings for the location data.

[sparkweaver]

After reading the Microsoft documentation and attempting to find relevant blog discussions, I have not found a resolution or any leads addressing the issue of duplicate trigger events in the application.

The decision to temporarily stop this investigation is due to encountering another problem during real-life testing. This new issue is likely to require a change to the application's current structure, which could potentially resolve or render the duplicate trigger issue obsolete. #16

[sparkweaver]

As the current version of the application does not use geolocation, I am closing this issue for now. I will revisit and potentially reopen this issue when. There is a need to re-implement the geolocation feature.