Possible asynchronous bug in NetworkOperationsHandlerImpl .

[gmpassos]

operations should be populated before schedule.

This line

operations[id] = op

should be placed before:

ioScheduler.schedule

The only thing that avoids an asynchronous bug is the delay of the operation execution,
what is not a correct pattern for synchronized data.

It's possible to have the operation executed before the operations[id] = op write.

kin-android/base/src/main/java/org/kin/sdk/base/tools/NetworkOperationsHandler.kt

Line 224 in 07dd338

synchronized(operations) { operations[id] = op }

kin-android/base/src/main/java/org/kin/sdk/base/tools/NetworkOperationsHandler.kt

Line 219 in 07dd338

expiryFuture = ioScheduler.schedule(

[Blahartinger]

feel free to submit a pr with your proposed change along side appropriate unit tests