Eventdispatcherissue (#35) (#54)

Fixed Timing issue with Activate() & Track() being called sequentially
optimizely · Jan 22, 2018 · 5df7cfb · 5df7cfb
1 parent 49b7e5d
commit 5df7cfb
Showing 1 changed file with 3 additions and 5 deletions.
diff --git a/OptimizelySDK/Event/Dispatcher/HttpClientEventDispatcher45.cs b/OptimizelySDK/Event/Dispatcher/HttpClientEventDispatcher45.cs
@@ -41,7 +41,7 @@ static HttpClientEventDispatcher45()
  /// <summary>
  /// Dispatch an Event asynchronously
  /// </summary>
- private async void DispatchEventAsync(LogEvent logEvent)
+ private async Task DispatchEventAsync(LogEvent logEvent)
  {
  try
  {
@@ -68,13 +68,11 @@ private async void DispatchEventAsync(LogEvent logEvent)
  }
 
  /// <summary>
- /// Dispatch an event Asynchronously by creating a new task and calls the 
- /// Async version of DispatchEvent
- /// This is a "Fire and Forget" option
+ /// Dispatch an event
  /// </summary>
  public void DispatchEvent(LogEvent logEvent)
  {
- Task.Run(() => DispatchEventAsync(logEvent));
+ Task.Run(() => DispatchEventAsync(logEvent)).Wait(); 
  }
  }
 }