Closed DanielTamm closed 1 year ago
This issue has been ignored for months. It is not acceptable to ignore crashes reported by paying customers. Most open source projects have better follow-up and error handling, and this is a commercial package that can cost its (paying) users money for every crash.
Hello and thank you for your patience! 5.4.1 was released to resolve this issue. Please let our Customer Success Team know if this hasn't been resolved for your integration.
We released our app this week, after updating to 5.4.0 as this version seems to fix https://github.com/iovation/deviceprint-SDK-iOS/issues/35. After releasing, we saw a relevant number of crashes in the framework.