Mobile data loss and 100% loss about reactivenetwork

[pwittchen]

Thank you for reporting that issue. This library is not designed to handle situations mentioned by you. UNKOWN status should be set in case if no status was set already. I think, it shouldn't occur in another situations. You can optionally test your case with OFFLINE status.

I'm not sure how to handle your case with mobile data loss and also how to test it properly. I'm not sure if I can reproduce such situation e.g. in a unit test. Code snippet provided by you is quite "hacky" and it uses reflection. I would rather avoid that, because it makes apps slower and is possible source of bugs and Runtime Exceptions.

If you have any idea how to solve this problem in a right way or have any ideas how to test it, your comments (and comments of anyone) are welcome.

I'll read more about this problem. After gathering more information, it will be easier to solve it.

[pwittchen]

I think, the right way to solve your problem could be usage of TelephonyManager and PhoneStateListener. It may be an idea for a new project, because this library could become to heavy if we throw everything in it.

[JosiasSena]

Thanks for the quick response!

Sounds good man, just thought it would be worth mentioning it.

Thanks anyways, ill keep on looking into it a bit more and finding the best way to do this in combination with your library.

[pwittchen]

As we discussed it in #282, this issue should be resolved within a separate project with different responsibilities. I have plans to create another library to address this issue, but I need to find a time for that. This issue can be closed for now.