Marko Pejovic

@otymartin, @arm0nic, @clopex, @ramonilho and @andrew-muzmatch - thank you for reporting and our apologies for delay in resolving this issue. We will be looking into this issue shortly. In the...

Today, we have rolled out 5.0.1 that we believe resolves this issue. Please update and do not hesitate to reopen if you encounter it again.

@Ariandr unfortunately, I'm not the owner of the pod at the moment therefore I've been unable to update it. Will try to sort this out asap for you. In the...

@Ariandr Podspec should now be updated

Thank you for reporting @mandarin6b0, looks like it might be the same issue again. If you have any additional stack traces, it might be useful. How often are you seeing...

@Ariandr and all - sorry for late reply, issue should defiantly be reopened. We had limited time available to deal with it. We are looking into @miketsprague pr as possible...

Thanks to great work by @miketsprague, we hope this issue should be resolved in 5.0.3 that is available now via CocoaPods. Thank you all for patience and apologies for inconvenience...