-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Question about behavior on observeWifiAccessPointChanges(context) #34
Comments
I have tested it, seems that it will not emit if the ap is disconnected |
Hi, I was AFK. I suppose you meant "phone is disconnected". I don't know what "app is disconnected" means in this context. You can clarify that. I think the library will not emit any "null" info when the phone is being disconnected. Moreover, it should scan networks even if the phone is not connected to any WiFi network. Regards, |
Hi, I refer ap as access point. I think it maybe reasonable for the library to emit something when disconnecting from an access point, so one can be notified and take action base on that emission. Thanks. |
@dokiKit I've made another library, which does that, because it's a separate responsibility. Some people want to monitor access points and others want to monitor connectivity only. Check it at: https://github.com/pwittchen/ReactiveNetwork. It's also based on RxJava, so you can make an interaction between different streams from various events coming from these two libraries (or any other RxJava stream). |
What will be the expected behavior when the ap is disconnected? Will it fires emission with a null Wifi info object?
Much Thanks!
The text was updated successfully, but these errors were encountered: