curl: (56) LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54 - dart

When I upgrade flutter, I came across with below error message.
curl: (56) LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
Failed to retrieve the Dart SDK from: https://storage.googleapis.com/flutter_infra/flutter/4737fc5cd89b8f0136e927b00f2e159444b95a73/dart-sdk-darwin-x64.zip
If you're located in China, please see this page:
https://flutter.io/community/china
Flutter 1.3.8 • channel beta • https://github.com/flutter/flutter.git
Framework • revision e5b1ed7a7f (6 weeks ago) • 2019-04-11 14:01:46 -0700
Engine • revision 4737fc5cd8
Tools • Dart 2.2.1 (build 2.2.1-dev.0.0 571ea80e11)
Running flutter doctor...
Downloading Dart SDK from Flutter engine 4737fc5cd89b8f0136e927b00f2e159444b95a73...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
What is this? what is the the problems?

Run these commands, it should solve the problem.
echo '--no-alpn' > ~/.curlrc
export HOMEBREW_CURLRC=1

its a network issue. If your internet is very slow and there are hiccups with network, you will face this error. Try to run again

VPN, if you are behind a firewall or using vpn, switch it off or ensure a good network connection.

errno 54 is "Connection reset by peer", which basically indicates a generic network connectivity problem.
I've had this exact failure with flutter upgrade during a temporary wifi hiccup.

Same problem trying to 'push' to GitLab.
Checked my account at GitLab website. There were errors, unable to retrieve my files on the website.
After about 30 min, the GitLab website started retrieving files normally and 'push' started working.

Related

Unable to use objection with corellium device

I am trying to use objection with my Corellium iOS device but I am getting the following error.
Using USB device `iPhone`
Unable to connect to the frida server: unable to communicate with remote frida-server; please ensure that major versions match and that the remote Frida has the feature you are trying to use
Corellium iOS Device Details: (iPhone 7 Plus | 14.3 | Jailbroken)
iOS Device Frida Version: 16.0.1
MacOS Frida Version: 16.0.1
For connecting to my virtual device I am using Tunnelblick and USBFlux. The connection is successful because I can SSH to my device and use frida-ps and frida-ls-devices without any issues.
However, when I issue the objection command, I encounter an error.
ubaidahmed#Ubaids-MacBook-Pro ~ % frida-ps -Ua
PID Name Identifier
3 ------- ---------------------------------
593 Cydia com.saurik.Cydia
546 DVIA-v2 com.highaltitudehacks.DVIAswiftv2
ubaidahmed#Ubaids-MacBook-Pro ~ % objection -g 546 explore
Using USB device `iPhone`
Unable to connect to the frida server: unable to communicate with remote frida-server; please ensure that major versions match and that the remote Frida has the feature you are trying to use
I even tried to upgrade the frida version to the latest 16.0.8 on my virtual iOS device but again faced the following error in cydia.
Steps followed for updating frida version:
Go to Sources
Edit > Add > https://build.frida.re - Add Source
Select the added entry - build.frida.re > All Packages
Select Frida (it shows latest Frida version) and click on Install
Installation fails
Edited: Also, I have tried to use objection with network option but still no success.
I have tried to provide as much information as possible related to the issue. Please help me out in resolving this strange issue.
If the connection via virtual USB doesn't work you can switch to a direct TCP connection. Execute frida -H IP:port and e.g. use port forwarding to get the frida server port to your local system.
The default frida-server port is 27042.
frida_16.0.8 in Cydia
The recent versions of the Debian package of frida-server don't work (see this issue). Keep your existing version or if you need to install it manually download the deb package of frida_16.0.7_iphoneos-arm.deb (do not use the 16.0.8 version, it is defect use at least 16.0.7 or older) from frida release page.
Download the deb package and install it manually by executing dpkg -i <frida...iphoneos-arm.deb>.

Unable to mount a developer disk image. iOS 15.4.1 - Xcode 13.3.1 (13E500a)

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

How to fix Failure “INSTALL PARSE FAILED NO CERTIFICATES” for Appium & Python?

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.

Failed to execute adb.exe when trying to run Xamarin.UITest

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.

Getting Error Flashing Android Things with Starter Kit

I recently picked up an Android Things Kit at Google Developer Days India. I was trying to setup it up via my Mac. I downloaded the Android Things Setup Utility from the Android things console. I tried to run it and it started installing the firmware. It stopped saying "Exit Status 1". What am i doing wrong?
Android Things Setup Utility (version 1.0.16)
============================
This tool will help you install Android Things on your board and set up Wi-Fi.
What do you want to do?
1 - Install Android Things and optionally set up Wi-Fi
2 - Set up Wi-Fi on an existing Android Things device
1
What hardware are you using?
1 - Raspberry Pi 3
2 - NXP Pico i.MX7D
3 - NXP Pico i.MX6UL
2
You chose NXP Pico i.MX7D.
Looking for devices... This can take up to 3 minutes.
found device
Unzipping image...
Flashing Android Things. This will take a few minutes...
*Do not disconnect or interrupt!*
target reported max download size of 419430400 bytes
sending 'bootloader' (559 KB)...
OKAY [ 0.018s]
writing 'bootloader'...
OKAY [ 0.250s]
finished. total time: 0.268s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 419430400 bytes
sending 'gpt' (33 KB)...
OKAY [ 0.004s]
writing 'gpt'...
OKAY [ 0.434s]
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.439s
target reported max download size of 419430400 bytes
Error: error flashing android things: exit status 1
Stopping adb server...
Stopped adb server...
For my case, it is because MacOS does not provide mke2fs.
I found one in the unzipped image folder (android-things-setup-utility/quickstart-temp/unzipped/mke2fs).
And run mv android-things-setup-utility/quickstart-temp/unzipped/mke2fs /usr/local/bin
Hope this can help.

Resources