Callback after in-app messages have finished displaying, even if there are no in-app messages

[iterable]

Callback after in-app messages have finished displaying, even if there are no in-app messages

[tapashmajumder]

I am going to close this issue now since it is taken care of in the beta release.

[tapashmajumder]

We are currently working on a big revamp of in-app messages. Please check out the 'in-app messages' section of README.md for new changes to in-app.

We are ready to roll out a beta version of in-app messages which will take care of this and much more. Would you be interested in that?

[vrutberg]

Yeah, that would be great. How do I access the beta version?

[tapashmajumder]

@vrutberg Use tag 6.1.0-beta1 from Github in your app. Sample Podfile is below

# Uncomment the next line to define a global platform for your project
platform :ios, '11.0'

# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!

target 'iOS Demo' do
  pod 'Iterable-iOS-SDK', :git => 'https://github.com/Iterable/swift-sdk.git', :tag => '6.1.0-beta1'

  target 'iOS DemoTests' do
    inherit! :search_paths
    # Pods for testing
  end

  target 'iOS DemoUITests' do
    inherit! :search_paths
    # Pods for testing
  end
  
end

target 'richMediaAttachments' do
    pod 'Iterable-iOS-AppExtensions', :git => 'https://github.com/Iterable/swift-sdk.git', :tag => '6.1.0-beta1'
end

[tapashmajumder]

@vrutberg If you send me your email address to tapash at iterable dot com I can add you to our Slack channel for beta feedback etc.

[vrutberg]

Great. I'm using Carthage but the setup should be similar. I will try it out and keep you posted! Thanks!

[vrutberg]

Migrating to the beta version seems quite straight-forward. Just as a sanity check, could you verify that this method of displaying in-app messages looks good to you?

func displayInAppMessages(completionHandler: @escaping () -> Void) {
    let messages = IterableAPI.inAppManager.getMessages()

    guard let first = messages.first else {
        completionHandler()
        return
    }

    IterableAPI.inAppManager.show(message: first, consume: true, callback: { _ in
        completionHandler()
    })
}

The idea is that we want to show one in-app message at a time. Please note that I'm also setting the inAppDelegate on the IterableConfig object and returning .skip in its delegate method.

[tapashmajumder]

Yes this looks great.

You may also want to consider using IterableCustomActionDelegate or IterableURLDelegate to handle clicks in your in-app instead of the completionHandler. See here https://github.com/iterable/swift-sdk#when-user-clicks-a-buttonlink-in-the-in-app-message

[vrutberg]

Great! Alright, thanks for the tip. I will look into that.

Do you have any expected release date for the new version?

[tapashmajumder]

Depends on whether we find any serious bugs in our beta. Hopefully in a few weeks.