-
Notifications
You must be signed in to change notification settings - Fork 100
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
Location Prompt Bug #1178
Comments
Tried to reproduce on my nexus 5 using the following builds: Was unable to reproduce on any of the listed builds. |
@g9singh Is there Moto Z Play Droid device on one of the device farms? |
Could not reproduce on Samsung Galaxy S6 on experimental or current production version from the Play Store. Currently running Android 8.0.0 |
@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. |
From my initial research we have 4 options for other device farm like services:
@c3bryant do you have any suggestions/preferences based on the CI/CD setup we have? |
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. |
Shuttle feature also creates another instance of the Location object and needs to be refactored to use stream from LocationDataProvider. |
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 |
Data logs going to the wrong folder has been resolved. |
Time Tracking: MA-34
From a user:
This is done when:
The text was updated successfully, but these errors were encountered: