Strange behaviour ActorSelection

Could it be that the value() of the Future is not completed yet?

If inside actor I’d recommend using messages rather than mixing resolveOne futures. There is an example of using Identify/ActorIdentity messages in the documentation.

Or perhaps you can pass in the ActorRef as a constructor parameter instead of using ActorSelection in the first place?

1 Like