From a bug to an on our iOS library

While you were all sleeping or on lazy coffee-breaks, our developers were like Batman and Robin fixing a library bug that was connected with the AFNetworking library.

Within 24 hours, the Filepicker iOS library was upgraded to reflect this change to version 4.2.2, while our AFNetworking library was updated to version 2.5.3.

That is how we roll at Filepicker. Developers are not allowed to sleep if they don’t find a bug and fix it quickly. Okay, this isn’t (that) true.

The bug issue was a security one. It transpired that because of a logic flaw in the latest version of the AFNetworking library, SSL MiTM attacks were feasible in apps using version 2.5.1.

Once we identified and rectified the issue, we bumped the minimum version of the AFNetworking dependency to 2.5.3.

The pros and cons of using AFNetworking –  the networking library for iOS and Mac OS X – is one that developers love only to spend hours debating over. But let’s face it, it’s one of the best developer communities out there, powering the most popular Apple apps on the market. What’s not to love? And here we are working our thing.

Example of changed file on our AFNetworking library : Podfile


What to do now? Our library users will have to update to our newest version, either by updating our library or changing the version of AFNetworking in your own code.

On a side note, our developers are now using the Filepicker Twitter account to quickly announce all upgrade/product issues and news. Reach out to us if you have any queries.




Read More →