You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They report to us that after they show an alert and tap the Cancel button, they cannot trigger an expected block.
Our SDK just calls a standard UIView dialog to display notifications, allowing the user to cancel or to tap Continue and accept a redirect to a deep link in the app or a URL.
We've never had a partner trying to use our SDK in the same app with UIAlertView-Blocks before, and although we're going to try and get familiar pretty quickly, I thought it was worth checking with you: do you have any idea what the problem might be?
I'm adding one screen cap in which they modified the target membership and managed to finish their callback, in case it's helpful.
If you have any insights, much appreciated. I know you don't know our SDK, either, but since we're very generic in terms of our UIView, perhaps you've seen a similar issue in other contexts, and might be able to clue us quickly. Thanks!
The text was updated successfully, but these errors were encountered:
Hey, Ryan, we have a development partner (with an offshore dev team) trying to integrate our notifications manager, which is here: https://github.com/mobiquity-networks/MNNotificationsManager-iOS-SDK
They report to us that after they show an alert and tap the Cancel button, they cannot trigger an expected block.
Our SDK just calls a standard UIView dialog to display notifications, allowing the user to cancel or to tap Continue and accept a redirect to a deep link in the app or a URL.
We've never had a partner trying to use our SDK in the same app with UIAlertView-Blocks before, and although we're going to try and get familiar pretty quickly, I thought it was worth checking with you: do you have any idea what the problem might be?
I'm adding one screen cap in which they modified the target membership and managed to finish their callback, in case it's helpful.
If you have any insights, much appreciated. I know you don't know our SDK, either, but since we're very generic in terms of our UIView, perhaps you've seen a similar issue in other contexts, and might be able to clue us quickly. Thanks!
The text was updated successfully, but these errors were encountered: