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
It tries to execute otool "#{File.expand_path(app)}"/* -o - which if I run directly from the command line I get a bash error:
Argument list too long
It seems there are too many files (2452) in my app bundle. I think this should be a little smarter about locating the app binary, maybe by looking for a file with the same name as the app bundle, or by using find to list any executables.
The text was updated successfully, but these errors were encountered:
Actually since the app binary has to be named the same as the app bundle, I think we could just use:
The executable name can be found by inspecting the Info.plist CFExecutableName key.
calabash-ios check
I am not a fan of that command; it needs to be fixed.
If you wanted to take a shot at fixing it, I would use something something like this:
app = RunLoop::App.new(< path to bundle >)
executable_name = app.executable_name
path_to_executable = ...
!`xcrun strings "#{path_to_executable}" | grep -E 'CALABASH VERSION'`.strip.empty?
# maybe for backwards compat we need to use otool; I will think about it.
When I try to run
calabash-ios check
on my project, I always get an error, even when I specify the full path manually:I tracked the problem down to calabash-ios-setup.rb:
https://github.com/calabash/calabash-ios/blob/master/calabash-cucumber/bin/calabash-ios-setup.rb#L268
It tries to execute
otool "#{File.expand_path(app)}"/* -o
- which if I run directly from the command line I get a bash error:It seems there are too many files (2452) in my app bundle. I think this should be a little smarter about locating the app binary, maybe by looking for a file with the same name as the app bundle, or by using
find
to list any executables.The text was updated successfully, but these errors were encountered: