-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flick not working with iOS 10 Xcode 8 #10
Comments
flick uses idevice library, you need to uninstall the library and install with HEAD, to get it working with ios10 |
brew uninstall ideviceinstaller |
thank you @saikrishna321! @philipsTanoto please follow this instructions to reinstall ideviceinstaller and try again. |
Im setting this to wontfix. If the steps @saikrishna321 didn't help then I will reopen. |
It is working now, thanks @saikrishna321 @isonic1 ! |
@isonic1, libmobiledevice working good with ios11, |
Hmm, you went through the steps to uninstall and reinstall the ideviceinstaller libraries? is it just logs that doesn't work or can you capture a screenshot on iOS with flick? If the latter, it could be an issue with ideviceinstaller needing updating for iOS 11. |
at first idevicesyslog not working with ios11 but flick still get error |
Ah ok. Yeah, probably brew hasn't got the latest fix that was put in for the issue below. I don't have ios 11 installed yet. would you mind trying the command below to install the iOS 11 libimobiledevice libraries below? libimobiledevice/libimobiledevice#510
|
its not helped me if update libmobiledevice if uninstall/install libmobiledevice |
ah, bummer was hoping that would work. iOS 11 isn't officially released until next week. Im hoping brew will have the updated fix for it by then. |
sorry, but I don't understand |
@alter-al what is the issue your facing ? wat does flick log say ? |
Thanks @saikrishna321 . Yes, please run flick with --trace and copy paste the output in the terminal. Thanks. |
@alter-al i use flick and it works fine with iOS11 ... |
@alter-al try now with the latest gem. Apparently, iOS 11 removed the ability to validate a paired device so tweaked that logic a bit. Make sure you have latest Xcode and command line tools installed and the device is not locked. Also, make sure you can see the Developer menu options in the Settings. |
@isonic1, thank you! When updated flick to 0.4.2, all works awesome (even with XCode 8.3.3) |
Not able to get any video using the command "flick video -a start -p ios -s 0.5 -c 6000" followed by "flick video -a stop -p ios -s 0.5 -c 6000" on Xcode 8, iOS 10.
No file was created, and "error: No such file or directory - (<temporary_file_path>, <current_working_directory>), User --trace to view backtrace." was observed.
same error message with --trace:
note: username, directory and UDID is removed from log for privacy.
/Library/Ruby/Gems/2.0.0/gems/flick-0.2.4/lib/flick/video.rb:142:in
rename': No such file or directory - (/Users/<user_name>/.flick/<UDID>.mp4, /Users/<user_name>/<UDID>.mp4) (Errno::ENOENT) from /Library/Ruby/Gems/2.0.0/gems/flick-0.2.4/lib/flick/video.rb:142:in
mp4'from /Library/Ruby/Gems/2.0.0/gems/flick-0.2.4/lib/flick/video.rb:130:in
stop_screenshot_recording' from /Library/Ruby/Gems/2.0.0/gems/flick-0.2.4/lib/flick/video.rb:51:in
stop'from /Library/Ruby/Gems/2.0.0/gems/flick-0.2.4/lib/flick/video.rb:25:in
run' from /Library/Ruby/Gems/2.0.0/gems/flick-0.2.4/bin/flick:32:in
block (2 levels) in <top (required)>'from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:178:in
call' from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:178:in
call'from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:153:in
run' from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in
run_active_command'from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/runner.rb:68:in
run!' from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in
run!'from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/import.rb:5:in `block in <top (required)>'
The text was updated successfully, but these errors were encountered: