I am trying to implement DTLS in my Android client using openssl/bio.h library.
The same does not cause any errors in iOS, while in Android..the DTLS handshake failure gives the following error
ssl3_write_pending:BIO_NOT_SET
I do not understand that error, has anyone tried this before or faced this issue? Did not find much help through google
I got the DTLS Handshake working after changing my DTLS code ,which was earlier using OpenSSL TO BoringSSL.I changed all the functions signature from that of OpenSSL to BoringSSL.
Related
Is anyone who is using Raygun in their Android apps seeing this error exception:
java.lang.NoClassDefFoundError: Failed resolution of: Lorg/apache/http/conn/util/InetAddressUtils;
at main.java.com.mindscapehq.android.raygun4android.messages.NetworkInfo.readIPAddress(SourceFile:117)
at main.java.com.mindscapehq.android.raygun4android.messages.NetworkInfo.<init>(SourceFile:20)
at main.java.com.mindscapehq.android.raygun4android.messages.RaygunMessageDetails.setNetworkInfo(SourceFile:61)
at main.java.com.mindscapehq.android.raygun4android.RaygunMessageBuilder.setNetworkInfo(SourceFile:81)
at main.java.com.mindscapehq.android.raygun4android.RaygunClient.buildMessage(SourceFile:508)
at main.java.com.mindscapehq.android.raygun4android.RaygunClient.send(SourceFile:221)
This exception is very intermittent, but when it does happen, it always occurs when the app calls RaygunClient.send(...). I'm using Raygun in my app to report error conditions such as a failed webservice call, however, when I report this to Raygun it crashes my app!
The release of v3.0.6 includes fixes that address the problems seen with InetAddressUtils NoClassDefFoundError exceptions. Please update to release v3.0.6 and let us know if the problems persist.
Please see our documentation on how to update. https://raygun.com/documentation/language-guides/android/crash-reporting/installation/
Regards,
Mitchell.
I am getting this error on compiling react native project using the expo framework.
I am getting no stack trace on my terminal but this is the error response on expo client.
http://biobekia.com/public/uploads/bekia-orders/20181218225953fsqRKer87zZBoGMsXWEn7gUm7pOFt3Z4.png
http://biobekia.com/public/uploads/bekia-orders/201812182259531cPLOHvayH5qLSw5WiQdnsxs2f01e4ri.png
For some reason clearing cache and recompiling fixed the issue, maybe it was an encoding issue that resulted in a tofu Character or something like that.
I was trying to open cache.properties.lock file present in .gradle
and suddenly Android Studio got crashed with Incompatible magic error popup.
How to fix this issue? No idea.
I also struggled with this issue a lot while we were sending JAVA classes in an enterprise - this is primarily caused when class (compiled) classes that are sent over mails as attachments and the proxy servers tampers with the content.
This can happen when using a proxy server, and especially when the CLASS files were sent as .TXT extensions to avoid PROXY/FIREWALL blockings to secured enterprise environments.
When in a call using the Sinch SDK on Android, the following error is thrown:
09-14 17:06:38.223 28454-28484/com.callcasual.callcasual E/sinch-android-rtc﹕ ERROR ; (17: 6:38:237 | 1) 28493; (voe_audio_processing_impl.cc:857): GetEcMetricsStatus: not supported
When searching for that error it appears to be an issue with WebRTC, however I cannot find a way to solve the issue.
This is only indicating that echo metrics are not available, the voice will go through fine during the call anyway. Why WebRTC logs this as an error I'm not sure but we are looking at disabling this in a future release of the Sinch SDK.
I use OpenSSL to establish a secured connection with my local HTTPS server. The server is really simple as I basically used the Boost Asio example but only improved a bit.
The solution works on Win7 64b using OpenSSL-Win32 and the certificates which comes with installer downloaded here.
I have ported the solution on Android. The Android OpenSSL port is from here.
Everything works fine until the use_tmp_dh_file method is called:
_context.use_tmp_dh_file("/sdcard/Download/PEM/dh512.pem");
It always ends up with the Fatal signal 11 (SIGSEGV) at 0x00000014 (code=1) error.
I use certificates server.pem and dh512.pem from the /apps folder of Android OpenSSL port.
Does anybody have an idea what is wrong?
EDIT:
Using a dh file is not mandatory, it works without it, but I am only a one step further because now it fails when starting handshake:
boost::system::error_code error;
socket.handshake(boost::asio::ssl::stream_base::server, error);
Where socket is instance of:
typedef boost::asio::ssl::stream<boost::asio::ip::tcp::socket> sslSocket;
It ends up with the same error as above. It seems to be an Android OpenSSL-Boost ASIO issue.
The answer on this particular question is short and simple, but it was quite hard to find it. The native library implementing my HTTPS server was interfering with the other native library using OpenSSL as well.