Native SSL provider not available under Windows after update to 0.8.1

I have use pushy for a long time, and it is really good for me. It works well when I use version 0.7.2, and this is my maven pom.xml:

        <dependency>
            <groupId>com.relayrides</groupId>
            <artifactId>pushy</artifactId>
            <version>0.7.2</version>
        </dependency>
        <dependency>
            <groupId>io.netty</groupId>
            <artifactId>netty-tcnative-boringssl-static</artifactId>
            <version>1.1.33.Fork17</version>
        </dependency>

but when I just change the versions , it can not work:

        <dependency>
            <groupId>com.relayrides</groupId>
            <artifactId>pushy</artifactId>
            <version>0.8.1</version>
        </dependency>
        <dependency>
            <groupId>io.netty</groupId>
            <artifactId>netty-tcnative-boringssl-static</artifactId>
            <version>1.1.33.Fork22</version>
        </dependency>

The log is :

Native SSL provider not available; will use JDK SSL provider.

So how can I solve this problem?

[ShanAmos]

@petrdvorak everything is ok, Thank u all guys

[jchambers]

Folks, I’ve just merged #392, which means that Pushy now depends on Netty 4.1.6. I believe that should address the initial issue.

As for questions about general ALPN configuration and trouble-shooting, I’d ask you to move the discussion to the Pushy mailing list because:

1. The mailing list has a wider audience, and you’re more likely to find somebody who has experience with your particular circumstances on the mailing list.
2. Posting your question to the mailing list can help other people who are having the same problem.
3. Because there isn’t a bug to fix or a feature to add, we can’t reasonably solve your problem by making any kind of engineering change.

I emphasize that we’d be happy to help, but let’s move this conversation to a different venue. Thanks!