3.0.1 Upgrade Broke Working Profile on Client

[MisterSurface]

This was the working configuration I had before the latest upgrades in February. I am on the current 3.0.1 Google Play upgrade. As others have pointed out the problem I appear to be having is that TLS-ECDHE-ECDSA-WITH-AES-256-GCM-SHA384 is no longer working.

I am adding this because it applies to 3.0.1 and others had mentioned problems about a previous version. I have imported all of my certificates and keys onto the Android keychain as well as through the import feature in OpenVPN on the client. I have also specified settings on the OpenVPN client where necessary e.g. ipv4 only, uncheck DNS override, no compression, etc.

View OriginalClient Config

client
dev tun
proto udp4
remote SCRUBBED SCRUBBED
redirect gateway def1
dhcp-option DNS 208.67.222.222
remote-cert-tls server
mssfix 1400
tun-mtu 1400
cipher AES-256-GCM
tls-version-min 1.2
tls-cipher TLS-ECDHE-ECDSA-WITH-AES-256-GCM-SHA384
auth-nocache
chroot jail
auth-user-pass
auth SHA512
prng blake2b512 64
nobind
float
key-direction 1
<ca>
-----BEGIN CERTIFICATE-----
SCRUBBED LEAF
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
SCRUBBED ROOT
-----END CERTIFICATE-----
</ca>
<tls-auth>
-----BEGIN OpenVPN Static key V1-----
SCRUBBED
-----END OpenVPN Static key V1-----
</tls-auth>

[MisterSurface]

Looks like there was some progress after the latest update but there are still errors - it doesn't show a new version but I just got an update to the app from google play today - 2/21/2018.

The new error that is showing up with a client profile and server configuration that worked prior to all of these updates is:

TLS Error: incoming packet authentication failed from [AF_INET]IP:port

config from previous post in this thread still applies

[MisterSurface]

Looks like things are back to normal. previously posted profile is now working just fine.