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

Integration with Google/Apple contact tracing API? #64

Open
leonoverweel opened this issue Apr 18, 2020 · 4 comments
Open

Integration with Google/Apple contact tracing API? #64

leonoverweel opened this issue Apr 18, 2020 · 4 comments
Labels
question Further information is requested

Comments

@leonoverweel
Copy link

Since the Apple + Google contact tracing API will be the only way to have the level of Bluetooth access required to make contact tracing work reliably (at least on iPhones when the screen is off or app isn't in the foreground), is TCN compatible wit that API?

I did a quick scan through the README.md and didn't find any mention of it; could someone clarify? If you're not planning to integrate, how are you planning to work around this limitation?

Thanks!

@kategallagher kategallagher added the question Further information is requested label Apr 23, 2020
@seriyvolk83
Copy link

Bluetooth will work even if the app is in background. There is no issue here.

@xuiqzy
Copy link

xuiqzy commented Jun 3, 2020

Could you elaborate on this since the table on the bottom of the readme seems to indicate that there are non optimal workarounds needed for the background case in iOS, especially when both are in the background?
Would an integration with these APIs be possible?

@rajagottumukkala
Copy link
Contributor

We have tested with two iOS devices. When the phones are locked, its complete stop. No exchange of tokens. Also, here is a good explanation https://www.youtube.com/watch?v=YHbl9IT67hs

So this is definitely a limitation, as you can imagine, phones will be locked majority of the time in a day.

@ziyangji
Copy link

I noticed it addressed in the Readme file

A nearby Android device acts as a bridge. It receives TCNs through “central” write operations (see 3rd row above) and adds them to a rotating list to broadcast alongside its own TCN.

It seems we must have a third android device

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

6 participants