Nate Ridderman
Nate Ridderman
I came here wondering about the same issue. I think the proposed solution makes sense.
I was having trouble with binding in onStart and unbinding in onStop. When I leave the app and come back, it's not subscribed to the render calls. I'm not sure...
Figured out my issue with onStart/onStop. I was calling `disposables.dispose()` instead of `disposables.clear()` in onStop, preventing it from accepting new disposables. @kioba lmk if you get stuck on a PR
At a minimum, you should add the unregister step to your README. Most users of your library will want to do this.
Also email is supposed to only allow 64 chars for the local part -https://en.wikipedia.org/wiki/Email_address#Syntax
Same problem here. I ended up using setHeaderParam() which is simpler anyways.
Actually createBond returns immediately, and you need to create a broadcast receiver to listen for the updated bond states. https://developer.android.com/reference/android/bluetooth/BluetoothDevice#createbond Here's an example: https://stackoverflow.com/questions/18197444/android-bluetooth-low-energy-pairing?rq=1 The receiver operates the same whether...
Right, they are related but slightly different concepts. This site has a good explanation - https://eewiki.net/display/Wireless/A+Basic+Introduction+to+BLE+Security#ABasicIntroductiontoBLESecurity-PairingOverview:
When you say it doesn't work well with unit tests, do you mean the dependency on Robolectric or are there additional things to be aware of?
I'm seeing this as well. Appium 1.9.1