I'm trying to copy the photos off my iPhone 5S. When I plug in my phone (I have the screen unlocked), I get an "Unhandled Lockdown error" and also when I try to use the File browser. I've seen -3 and -16 (and maybe -5 and -20, not sure).
I have tried using some of the idevice* command line tools but with very limited success: idevicepair pair works, as does idevicepair validate. But ideviceinfo fails with GnuTLS error: A TLS packet with unexpected length was received.
I'm running Ubuntu 14.04 and iOS 10. This is a new problem since upgrading to iOS 10.
You must compile it yourself, as it has not been updated in the repos.
https://gist.github.com/Aaahh/1e354ee60dbe40f64efe7e4f98f720d4
Related
iOS: 15.4.1 , Xcode: 13.3.1 (13E500a), macOS: 12.3.1 (21E258)
Hi, I was originally trying to remote debug in Terminal by:
idevicedebugserverproxy -d 9999
then in a lldb session:
process connect connect://localhost:9999
but lldb returned:
error: failed to get reply to handshake packet
and idevicedebugserverproxy returned:
main: Waiting for connection on local port 9999
main: Handling new client connection...
main: Waiting for connection on local port 9999
connection_handler: client_fd = 4
Could not start debugserver on device!
Please make sure to mount a developer disk image first.
I did some research saying that build an app with Xcode would automatically mount the disk image for us, so I simply built and ran the default "hello world!" app on the phone, but still receive above errors. I also rebooted the phone many times with no luck.
So I decided to mount it manually with the latest developer disk image 15.4 by:
ideviceimagemounter /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/15.4/DeveloperDiskImage.dmg /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/15.4/DeveloperDiskImage.dmg.signature
but kept receiving this error:
done.
Mounting...
Error: ImageMountFailed
I'm assuming developer disk image have to match the phone's version, but I can't find the 15.4.1 version.
What am I missing or doing wrong?
I managed to solve this problem by uninstalling libplist, usbmuxd, libimobiledevice, ideviceinstaller from brew and manually build the latest version from GitHub.
done.
Mounting...
Done.
Status: Complete
I am making an automation script to automate a Real SMartphone Android 8.1:
Environment
Python 3.7
Windows 10 64Bits
Build-tools 29.0.3
java version "1.8.0_241"
Appium 1.17.1
Node v12.15.0
sdkmanager 4.0.1
ADB (Android Debug Bridge) version 1.0.41
Version 30.0.3-6597393
When I run my script, I get these error message:
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
--> We can't open Instagram. Please check if device is connected. Let's try again!
Message: An unknown server-side error occurred while processing the command. Original error: Performing Push Install
C:\Users\Nino\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk: 1 file pushed, 0 skipped. 87.8 MB/s (470052 bytes in 0.005s)
Appium log file:
https://github.com/gauthierbuttez/public/blob/master/appium_issue04082020.log
What I've tried:
I added this desired capability:
desired_caps['remoteAppsCacheLimit'] = 0
It didn't help.
I reset factory my Android device but it didn't help.
Does anyone already faced this issue?
Try to add noSign: true to capabilities. It might help.
I also suggest manually removing Appium Settings and Instagram apps before starting a new session.
Getting UiAutomator exited unexpectedly with code 0, signal null error on appium version v1.10.0
My Appium server logs :-
Change Android version (I switch it to Pie)
Restart Appium server
Close and Re-open AVD device
In my case, the app was blocking further process. Due to some installed security features, immediately after app launch, all USB ports connections were refused by the app itself. After, the developers shared another apk with disabled security features, the test run was completed
Seems like version issue... Ensure you have the latest sdk and it is updated for the Android version you are using.
Ensure that device is connected properly. At times the USB connection of not done correctly causes this issue.
Phone reboot worked for me. It's a process stuck on Android, at least that was it for me. You could also try
adb shell ps | grep com.android.commands.monkey | awk '{print $2}' | xargs adb shell kill -9
if you do not wish you reboot your phone.
Appium knows about this issue but closed it. I would recommend to move to Espresso for less headaches. Appium is and always will be a beta-state.
For me it was a cable issue. Try changing cables, too. Changing the automation name to uiAutomator1 or uiAutomator2 didn't make any difference, it was still failing. I even tried downloading Android SDK to match version 8, 9, 10.
My tests were running on 6 different real devices. The same script was running fine on 5 devices but throwing uiAutomator stopped unexpectedly for one device.
When I connected the same device with another cable it worked fine.
So when things go crazy, give a break, rethink, stop pulling hair. solution might be super simple.
I'm trying to setup a Xamarin UITest without any luck.
When I try to run 'all tests', I get the following error:
execute: C:\Users\Brandon\AppData\Local\Android\android-sdk\platform-tools\adb.exe devices - exit code: 1
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037: Only one usage of each socket address (protocol/network address/port) is normally permitted. (10048)
List of devices attached
adb server version (39) doesn't match this client (36); killing...
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon
ADB seems to be started just fine and the weird thing is that it seems to be using an adb version from another user, even though..
1) Tools > Options > Xamarin > Android is set to different path than the above-mentioned, for the Android SDK.
2) There is no system environment path variable that I can find for the above-referenced adb.exe path!
Am I missing something?
In my case it was Android Emulator version mismatch. Somehow Emulator got updated to the newer version:
After uninstalling Emulator, switching Feed to Microsoft instead of google and re-installing Emulator - error was gone and everything worked just fine.
I am trying to run this weather tutorial app on an actual iPhone (I've got it working on the emulator so far).
[ERROR] Failed when running /usr/bin/codesign: codesign_allocate:
object:
/Users/cdplMBP17/Documents/AppDev/trigger/development/ios/device-ios.app/Forge
malformed object (unknown load command 43)
/Users/cdplMBP17/Documents/AppDev/trigger/development/ios/device-ios.app:
object file format unrecognized, invalid, or unsuitable
Thanks in advance.
This can happen if you have an older version of Xcode or if the Xcode command line tools have got into a bad state.
I recommend trying the following
1) Make sure the latest Xcode is installed from the app store.
2) Make sure the command line tools are installed and Xcode is aware they are installed. To install the command line tools, open the Xcode preferences and go to Downloads, there should be an install button next to Command Line Tools (see the image below).
If this doesn't help then your version of OS X and the full log output from the failed run on a device would be helpful.