Location Prompt Bug

[a6wu]

Time Tracking: MA-34

From a user:

I discovered a bug in the mobile app. When I open the app it asks if I want to turn on my Location for a better experience. When I say No, it pops up again for a total of 5 times before the app crashes. My device is an Android – Moto Z Play Droid.

This is done when:

• Shuttle location provider refactored
• Wayfinding location provider refactored
• FutureBuilder used inside Wayfinding StreamBuilder for local permission availability (@asg003)

• PR 1405 Test Plan PASS on iOS
• PR 1405 Test Plan PASS on Android

[g9singh]

Tried to reproduce on my nexus 5 using the following builds:
7.2.15 PROD
7.2.14 Prod
DEV build from experimental branch

Was unable to reproduce on any of the listed builds.
The device is running android version 6.0.1.

[a6wu]

@g9singh Is there Moto Z Play Droid device on one of the device farms?

[gmihir]

Could not reproduce on Samsung Galaxy S6 on experimental or current production version from the Play Store. Currently running Android 8.0.0

[g9singh]

@a6wu I just ran it on device farm.

I couldn't find Moto Z in the device list so I tried similar devices. Unfortunately they do not reproduce the bug.

[g9singh]

From my initial research we have 4 options for other device farm like services:

• Firebase test labs: https://firebase.google.com/docs/test-lab/android/available-testing-devices

  • doesn’t support Moto Z

• Kobiton: https://docs.kobiton.com/devices-list/

  • supports Moto Z and many other devices

• Sauce labs: https://saucelabs.com/platform/supported-browsers-devices

  • does not support Moto Z
  • appears to be more expensive than Kobiton

• Xamarin Test Cloud (Now App Center Test): https://docs.microsoft.com/en-us/appcenter/test-cloud/devices/android

  • does not Moto Z
  • supports many other devices

@c3bryant do you have any suggestions/preferences based on the CI/CD setup we have?

[anaaamika]

Reproduced on Samsung S7 running Android 8.0.0 using build 7.6.0 QA and 7.5.0 QA. App crashes in both instances whether accepting or declining to turn on device location.

[g9singh]

Upon further investigation, it seems that the app is requesting permissions again from the wayfinding feature. We already have a LocationDataProvider that handles the permissions and returns a stream of coordinates. Please use that instead of a creating a new instance of the Location object.

Once the wayfinding feature is refactored to use the LocationDataProvider the permissions issue should be resolved.

[anaaamika]

Shuttle feature also creates another instance of the Location object and needs to be refactored to use stream from LocationDataProvider.

[kevdesilva01]

Test passed but Scans are being logged in the wrong folder in S3. I opened a new issue after speaking with Alex regarding this. #1422

[c3bryant]

Data logs going to the wrong folder has been resolved.