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
I’m not sure what people use those actions for normally, but since we suppress output and the build still reports BUILD SUCCEEDED, there is no way to see that these actions have failed.
However, this problem also occurs with Xcode.app (no red), so it won’t be any different than what people are used to, but it would be nice to do the better thing, not just what Xcode.app does.
The text was updated successfully, but these errors were encountered:
I'll definitely look into this. I've used pre/post actions in the past for my testing scheme, to do things like run a small Ruby web server for acceptance testing HTTP operations (acceptance specs for LRResty are a good example of this).
I'll see if there is a workaround for this. My main priority is to get the build/clean/archive actions rock solid then start looking at translations for the likes of SenTest and Kiwi.
On further investigation, it seems that xcodebuild doesn't report the results of pre/post action scripts either, so I'm not sure we can do much about this. It might be worth filing a radar.
I’m not sure what people use those actions for normally, but since we suppress output and the build still reports
BUILD SUCCEEDED
, there is no way to see that these actions have failed.However, this problem also occurs with Xcode.app (no red), so it won’t be any different than what people are used to, but it would be nice to do the better thing, not just what Xcode.app does.
The text was updated successfully, but these errors were encountered: