[BUG] : java.lang.RuntimeException: org.apache.hc.core5.http.ParseException: Invalid protocol version; error at offset 0: <[0x2e][0x2f][0x30][0x31][0x32][0x33][0x34][0x35][0x36][0x37][0x38][0x39][0x3a][0x3b][0x3c][0x3d][0x3e]> about azure-notificationhubs-java-backend

[Gallaecio]

Sounds like https://issues.apache.org/jira/browse/HTTPCLIENT-2219

[dpozimski]

libs.zip
compiled version from https://github.com/Azure/azure-notificationhubs-java-backend/pull/149

[dpozimski]

you can install the file to your docker/local maven repository by executing:
mvn install:install-file -Dfile=".\libs\Notification-Hubs-java-sdk-custom-1.0.4.jar" -DgroupId="com.windowsazure" -DartifactId="Notification-Hubs-java-sdk-custom" -Dversion="1.0.4" -Dpackaging=jar -DpomFile=".\libs\pom.xml"

[jessHuh]

The POC provided by the customer uses different library versions and has extra dependencies that Azure Notification Hub(ANH) SDK doesn't. The customer may remove libraries that ANH SDK doesn't use and use the same library versions to resolve the issue. Unfortunately, we will not be able to provide support on fixing the customer's written codebase.

Closing the ticket as it is tested and verified with JDK 17.

1. Verified the fcm send test with ANH Java SDK 1.0.3 (https://github.com/Azure/azure-notificationhubs-java-backend/blob/main/NotificationHubs/test/com/windowsazure/messaging/e2e/RegistrationCrudsE2E.java#L837) works without errors.
2. The customer may run the test to check their FCM Notification. Note that, the e2eSetup.properties file is needed to be updated with the connectionstring and gcmkey.