Preventing a NullPointerException by checking the nodeLatencyVerifier reference first

This commit is contained in:
Nelson R. Perez 2018-10-01 23:58:03 -05:00
parent b37bb9dce0
commit 5ef4ebfca7

View file

@ -331,6 +331,7 @@ public class NetworkService extends Service {
mSelectedNode.setConnected(true);
// Updating the selected node's 'connected' status on the NodeLatencyVerifier instance
if(nodeLatencyVerifier != null)
nodeLatencyVerifier.updateActiveNodeInformation(mSelectedNode);
// Notifying all listeners about the new connection status
@ -568,6 +569,7 @@ public class NetworkService extends Service {
mSelectedNode.setConnected(false);
// Updating the selected node's 'connected' status on the NodeLatencyVerifier instance
if(nodeLatencyVerifier != null)
nodeLatencyVerifier.updateActiveNodeInformation(mSelectedNode);
@ -612,6 +614,7 @@ public class NetworkService extends Service {
mSelectedNode.setConnected(false);
// Updating the selected node's 'connected' status on the NodeLatencyVerifier instance
if(nodeLatencyVerifier != null)
nodeLatencyVerifier.updateActiveNodeInformation(mSelectedNode);
// We have currently no selected node