fix: First event being missed in iOS background worker

[mchudy]

I noticed a problem with the execution of the HomeWidgetBackgroundWorker. The first tap on my widget's button wouldn't execute the Dart callback the first time it had been called (with the app being terminated). I believe the if condition in run should be the other way around:

• if the setup is completed and the FlutterEngine is started we can send the event directly to the MethodChannel.
• if the setup is not yet completed we should add the event to the queue and when the background is initialized (HomeWidget.backgroundInitialized is received) the queue will be emptied and the event send to the existing method channel.

I'm also not sure if we need to get the dispatcher here and log it, but I leave it for you to decide.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3a1976c) 100.00% compared to head (e741465) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #188   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           69        69           
=========================================
  Hits            69        69           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ABausG]

Thanks for the fix! I actually noticed that this had issues but did not see that basically the actions in the if block where the wrong way around. I guess this might also fix #179 ?

[mchudy]

Not sure about that, what I'm currently doing is using background tasks to prevent the app from stopping, but I don't know if this should be the default behavior. #176 (comment)