ito-org / react-native-ito Goto Github PK

Convert the Android code to Swift.

Convert the Android code to Swift.

Add a client-side implementation for Private Set Intersection Cardinality, even though it does not work with the current A&G library.

See https://github.com/OpenMined/psi-cardinality for an open-source implementation.

Required for ito-org/ito-app#102

Currently, the BASE_URL is hardcoded:

private static final String BASE_URL = "https://api.ito-app.org";

By externalizing it as an environment variable, it will become possible to configure the BASE_URL during the build process and have different backends (e.g. staging vs production backend).

Possible solution: https://github.com/luggit/react-native-config

Convert the Android code to Swift.

Have the app connect to our backend(s) via a proxy server, mostly to hide the user's IP address.

It is unclear under which license this code is distributed

In the comments of this article link are critics on saving the timestamp with the token. We notice this critic and would like to discuss if we can improve that issue.

Currently iOS won't be able to build until this library can build. Caused by incomplete / unused code in ItoBluetooth.m / ItoBluetooth. Can we temporarily comment this file out until we have a proper implementation?

appstart after fresh installation crashes with following stacktrace:

04-11 20:42:42.581 29534 29534 E AndroidRuntime: FATAL EXCEPTION: main
04-11 20:42:42.581 29534 29534 E AndroidRuntime: Process: com.reactnativeapp, PID: 29534
04-11 20:42:42.581 29534 29534 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void org.itoapp.strict.service.ContactCache.setDistanceCallback(org.itoapp.DistanceCallback)' on a null object reference
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at org.itoapp.strict.service.TracingService$2.setDistanceCallback(TracingService.java:64)
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at com.reactlibrary.ItoBluetoothModule$2.onServiceConnected(ItoBluetoothModule.java:44)
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:1579)
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1607)
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:761)
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:98)
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at android.os.Looper.loop(Looper.java:156)
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6517)
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:942)
04-11 20:42:42.581 29534 29534 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:832)
04-11 20:42:42.583 1748 1903 I AppManager: app:com.reactnativeapp Notification update time:2666438869

• Use better proximity calculation, see e.g. http://www.pspachos.net/pubs/GIIS20181.pdf
• Limit signal strength for better privacy
• Import Bluetooth calibration data. Make sure that imported data is compatible with our BSD 3-Clause Clear license.

Convert the Android code to Swift.

Was wondering what is the typical workflow for your package and if it's ok to use it in our own app?

1. Is the IOS implementation still WIP?
2. For this to be reusable, perhaps network code should be stored outside of the module
3. Are you able to provide pointers of the expected API responses from the server?

Thank you so much. Hope we can work together

Certificate pinning: We currently rely on android to verify the server tls certificate. This can in theory allow mitm-attacks!

… upon isPossiblyInfected state change to true

Current protocol: https://github.com/ito-org/STRICT

Desired protocol: https://github.com/TCNCoalition/TCN