You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My name is Alejandro Mazuera-Rozo, I am a PhD Student at Universidad de los Andes, and at Università della Svizzera italiana. I am part of a research on the usage of network libraries within Android apps. As result of this we identified some code locations that might have network related problems.
In this case, we address the code locations that are related to a network request which is not being assessed on failure. In order to avoid misbehaviour when performing network operations it is recommended to handle failure scenarios.
In order to address this issue we recommend:
To add a try statement allowing you to define a block of code to be assessed while being executed.
To include a catch statement in which one defines a block of code to be executed if an error occurs.
Potential Code Location not handling failure scenarios when performing a network request
Dear Developer!
My name is Alejandro Mazuera-Rozo, I am a PhD Student at Universidad de los Andes, and at Università della Svizzera italiana. I am part of a research on the usage of network libraries within Android apps. As result of this we identified some code locations that might have network related problems.
In this case, we address the code locations that are related to a network request which is not being assessed on failure. In order to avoid misbehaviour when performing network operations it is recommended to handle failure scenarios.
In order to address this issue we recommend:
try
statement allowing you to define a block of code to be assessed while being executed.catch
statement in which one defines a block of code to be executed if an error occurs.Potential Code Location not handling failure scenarios when performing a network request
bo-android/app/src/main/java/org/blitzortung/android/jsonrpc/HttpServiceClientDefault.kt
Lines 39 to 42 in 2866251
The text was updated successfully, but these errors were encountered: