IOT Connection - java.lang.IllegalArgumentException: no NetworkModule installed for scheme “ssl”

[hardikdevios]

Describe the bug
After updating the AWS SDK Library to 2.71.0 I am getting the following exception from mqttManager?.connect() function

java.lang.IllegalArgumentException: no NetworkModule installed for scheme “ssl” of URI “ssl://xxxxxxxxxxxxxx-xxx.iot.xx-xxxx-1.amazonaws.com:8883”

Which AWS service(s) are affected?
AWS IOT

Environment Information (please complete the following information):

• AWS Android SDK Version: 2.71.0
• Device: Pixel 4a
• Android Version: Pie 9.0
• Specific to simulators: No

[tylerjroach]

@hardikdevios This looks like it is coming from the Paho client. Can you try these proguard rules?
eclipse/paho.mqtt.java#572 (comment)

[hardikdevios]

@hardikdevios This looks like it is coming from the Paho client. Can you try these proguard rules? eclipse/paho.mqtt.java#572 (comment)

Thank you, let me try it

[hardikdevios]

@tylerjroach Proguard rules didn't work, still getting the same error

[hardikdevios]

@tylerjroach Any idea, do we require any other proguard rules to get it working?

[hardikdevios]

@tylerjroach Any way solved the issue, so I am closing the ticket

[tylerjroach]

Sorry I had not gotten back to you yet but I am glad you resolved the issue. If there are any details that you can share, in case another customer runs into the same issue, it would be appreciated. Thanks!

[F1nny]

Thanks @tylerjroach for your help here, it appears that in the newer AWS SDK, the paho client SPI NetworkModuleFactory is now created as a service in the Android META-INF which was not the case in the prior versions (we hadn't updated since last year so was a bit of a jump). Due to some other factors our apk has to be resigned via command line which has always cleared the META-INF before resigning, and losing that service file is what caused the problem 😄 After reworking the resigning process, we're back to normal 🎉 Thanks again!