You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can be confirmed by turning on Swift Whole Module Optimisation for the Debug Configuration in the Build Settings, and running the tests.
I realise this is quite likely to be a Swift compiler bug, but having it recorded here might save someone some valuable time, and maybe there's a way to avoid this I'm not aware of.
Some context
We setup Embassy/Ambassador as the server for our UI tests and everything was working fine until it was running on our CI, where it would just hand endlessly. I eventually realised that this was because we were using a different Configuration and Cocoapods creates new Configurations to match any you added, but the pods themselves have settings that match those of their default Release config, with Whole Module Optimisation turned on.
A 'solution'
We've worked around the issue using the following Cocoapods post_install script (with inspiration taken from this old Cocoapods thread):
thanks for the report, that's a very interesting finding. I will look into that when I have time. I saw there is another issue open for similar hanging issue #30, not sure is that the same one, but will look into that later altogether.
This can be confirmed by turning on Swift Whole Module Optimisation for the Debug Configuration in the Build Settings, and running the tests.
I realise this is quite likely to be a Swift compiler bug, but having it recorded here might save someone some valuable time, and maybe there's a way to avoid this I'm not aware of.
Some context
We setup Embassy/Ambassador as the server for our UI tests and everything was working fine until it was running on our CI, where it would just hand endlessly. I eventually realised that this was because we were using a different Configuration and Cocoapods creates new Configurations to match any you added, but the pods themselves have settings that match those of their default Release config, with Whole Module Optimisation turned on.
A 'solution'
We've worked around the issue using the following Cocoapods
post_install
script (with inspiration taken from this old Cocoapods thread):The text was updated successfully, but these errors were encountered: