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

[ExposureNotifications] Crash on Nearby GetStatusAsync method #1094

Open
nc-kano opened this issue Feb 16, 2021 · 0 comments · May be fixed by #1231
Open

[ExposureNotifications] Crash on Nearby GetStatusAsync method #1094

nc-kano opened this issue Feb 16, 2021 · 0 comments · May be fixed by #1231

Comments

@nc-kano
Copy link

nc-kano commented Feb 16, 2021

Repro steps:
await NearbyClass.GetExposureNotificationClient(Application.Context).GetStatusAsync()

Expected:
Collection of ExposureNotificationStatus

Actual:
Crash because there is a cast from collection to single Enum. It shoud be casted to AbstractCollection instead of ExposureNotificationStatus

Additional:
EN api should not use the native device API to check the bluetooth/location status. Nearby API should be used instead to get the whole list of possible issues instead of getting only one status that can cover up all other issues. Nearby EN status provides 13 options, Xamarin.EN only 6 (and only 4 are used on Android)
https://developers.google.com/android/reference/com/google/android/gms/nearby/exposurenotification/ExposureNotificationStatus

@nc-kano nc-kano changed the title [ExposureNotifications] Crash on Nerby GetStatusAsync method [ExposureNotifications] Crash on Nearby GetStatusAsync method Feb 16, 2021
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