Increment version number when you make changes about conceal HOT 10 CLOSED

I'm not a maven expert and assumed that maven would reasonable cache based on a hash an not version number which was a bad assumption. The reason I didn't change the version number was because the major change was basically a third-party library upgrade. Since then, we've updated other code as well which was mistakenly picked up into the 1.0.0 release.

It seems that maven is forcing my hand here and I'll bump the version to the new version number and upload a new binary. Thanks for the report.

from conceal.

@siyengar I'm assuming this will solve the OpenSSL issue as well?

from conceal.

Yes it will @JaredBanyard

from conceal.

Great, I look forward to the resolution! Thanks for your time on this.

from conceal.

@siyengar Any progress on this? I would really like to patch the vulnerable version of OpenSSL.

from conceal.

I've uploaded a new version to 1.0.1 http://search.maven.org/#artifactdetails%7Ccom.facebook.conceal%7Cconceal%7C1.0.1%7Caar.asc. Could you verify that this works for you @JaredBanyard

from conceal.

@siyengar The package name for the SharedPrefsBackedKeyChain changed from com.facebook.crypto.keychain.SharedPrefsBackedKeyChain to com.facebook.android.crypto.keychain.SharedPrefsBackedKeyChain for some reason. But after fixing the import, it compiles and functions. Was that expected? I will update the APK and report on the play store notices.

from conceal.

@JaredBanyard yes, since this is a new release, I have improved some of the namespacing of packages. Thanks for being patient.

from conceal.

@JaredBanyard did that fix work for you.

from conceal.

@siyengar Yes! The warning from Google about the vulnerable OpenSSL version has gone away! Thanks for your time on this!

from conceal.