[grpc-io] Re: gRPC C++ Android 'Security handshake failed' issue

2023-02-23 Thread Artem V
Update: I've updated grpc to v1.53 and still getting the same error: LogPlayLevel: UAT: 02-23 22:51:34.793 23217 23654 D UE : [2023.02.23-18.51.34:793][ 0]Logproject: GRPC C:\Projects\project\grpc2\grpc\src\core\lib\transport\handshaker.cc::100::1: handshake_manager 0x79210acd40: error=O

[grpc-io] Re: gRPC C++ Android 'Security handshake failed' issue

2023-02-23 Thread Artem V
Update: I've updated grpc to v1.53 and still getting the same error: LogPlayLevel: UAT: 02-23 22:51:34.793 23217 23654 D UE : [2023.02.23-18.51.34:793][ 0]Logproject: GRPC C:\Projects\project\grpc2\grpc\src\core\lib\transport\handshaker.cc::100::1: handshake_manager 0x79210acd40: error=O

[grpc-io] Re: gRPC C++ Android 'Security handshake failed' issue

2023-02-23 Thread Artem V
Hi Richard. Yes this is censored ipv4. As I mentioned above 'domain and target address are the same as in working Windows build'. Adress is totally fine the problem is something else. среда, 22 февраля 2023 г. в 22:50:01 UTC+4, Richard Belleville: > > ipv4:xx.xxx.xxx.xxx:443 > > Did you censor

[grpc-io] Re: gRPC C++ Android 'Security handshake failed' issue

2023-02-22 Thread 'Richard Belleville' via grpc.io
> ipv4:xx.xxx.xxx.xxx:443 Did you censor the logs or is this really your target address? If this is not censored, then this is clearly not a valid ipv4 address. On Wednesday, February 22, 2023 at 5:44:52 AM UTC-8 Artem V wrote: > Greetings, > > We are trying to port our gRPC C++ solution we use