fix: addApplicationDelegate unavailable in iOS

[armandsLa]

I'm proposing a simple fix to avoid errors caused by NS_EXTENSION_UNAVAILABLE_IOS when adding home_widget to the widget target. This fix uses performSelector to bypass the NS_EXTENSION_UNAVAILABLE_IOS macro. It might not be ideal, but it works and is very simple.

[ABausG]

Ooh! This looks very nice. I tried to work around this by using some @available annotations but those seem to not correctly check at runtime. Will have closer look later today!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (cba8262) to head (dd044da).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #228   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           73        73           
=========================================
  Hits            73        73           

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

[ABausG]

Thank you so much for this!

I'd love to hear some more reasoning about your approach in comparison to an available check. Mostly to learn a bit more about iOS!

Also could you possibly add the pod spec adjustments needed for Interactivity to the example pod file? I noticed that this way the Integration Test Would fail without adjustments so it would be a great check

target 'YourWidgetExtension' do
   use_frameworks!
   use_modular_headers!

   pod 'home_widget', :path => '.symlinks/plugins/home_widget/ios'
end

[ABausG]

@armandsLa Do you still have time to finish this off?

[armandsLa]

Sorry for the late response, I've been very busy lately.

I've made changes to the Podfile as requested. I moved every target to the root level and added the necessary configurations. Previously, the targets were nested, which I had never seen before. Usually, every target is at the root level, and optionally, a shared_pods method is defined to keep everything DRY. In this case, it was not necessary, though.

[ABausG]

Had to make some adjustments to the Podfile in order to have integration tests pass. The nesting seems to be important to work correctly. Given that the RunnerTest nesting is also done by the default Flutter Project I feel this is fine. Most important thing the tests are passing again