For me it was rescanning for a service type while an identical service scan was already in progress. Stopping the previous scan first solved the issue and the _CFAssertMismatchedTypeID crash went away.
ecumedesjours
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Change the bundleID temporarily (repeatedly if needed) and it should treat the app as a new entry and pop up the message. Once you get the behavior you want, set the bundleID back to the original one.
Update: 3 months later the problem was resolved. We had to use the bank swift code and not the zengin code. Then everything went fine.