Illegal state exception in PIO.setConfig()

[shanestaples]

Currently, the two highest occuring crash for our app in Crashlytics are inside the PIO.setConfig() method. Below is the relevant portion of the two obfuscated logs, collected by Crashlytics. We're currently integrating version 3.2.2 of the PrintIO Android SDK.

Caused by java.lang.IllegalStateException
egsa.a (Unknown Source)
vbcp$amoc.a (Unknown Source)
vbcp$amoc.b (Unknown Source)
cfxv$1.a (Unknown Source)
cfxv$amoc.b (Unknown Source)
ktvz.a (Unknown Source)
ktvz.a (Unknown Source)
ktvz.a (Unknown Source)
ktvz.a (Unknown Source)
fwsw.a (Unknown Source)
fwsw.a (Unknown Source)
print.io.PIO.setConfig (Unknown Source)

Caused by java.lang.IllegalStateException
egsa.c (Unknown Source)
cfxv$amoc.b (Unknown Source)
ktvz.a (Unknown Source)
ktvz.a (Unknown Source)
ktvz.a (Unknown Source)
ktvz.a (Unknown Source)
fwsw.a (Unknown Source)
fwsw.a (Unknown Source)
print.io.PIO.setConfig (Unknown Source)

The crash distribution is as follows (for the highest occurring crash):
DEVICES:
73% Samsung
14% LGE
8% Motorola
5% Other

OPERATING SYSTEMS:
66% Android 5
29% Android 4
5% Android 6

[bomberaya]

Hi Shane, can you tell me which version of the SDK is producing these crashes?
This stack trace does not correspond to version 3.2.2 but to some older version,
and it is possible that the issue has been resolved already.
If you know the version used there, please let me know.

Thanks

[shanestaples]

@bomberaya Apologies, you are correct, I misread the merge history and release dates previously. The version corresponding to those logs should be v3.1.32. Can you please confirm whether this has been fixed in the most recent version of the SDK? Thanks!