Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App in the foreground,Message UI problem #127

Closed
wujunyang opened this issue Jul 25, 2019 · 1 comment
Closed

App in the foreground,Message UI problem #127

wujunyang opened this issue Jul 25, 2019 · 1 comment

Comments

@wujunyang
Copy link

Hello, I have successfully integrated Iterable-iOS-SDK, but when I tried to send push messages [Message Medium (Push)], if APP was running in the foreground(UIApplicationStateInactive), it found that the method of calling Iterable had no UI effect, received messages but did not show the UI, does SDK support this kind of display at present?

-(void)application:(UIApplication *)application didReceiveRemoteNotification:(nonnull NSDictionary *)userInfo fetchCompletionHandler:(nonnull void (^)(UIBackgroundFetchResult))completionHandler
{
[IterableAppIntegration application:application didReceiveRemoteNotification:userInfo fetchCompletionHandler:completionHandler];
}

I tried to see the effect of SDK implementation, that in the active state, they are all direct breaks.

IterableAppIntegration:

func application(_ application: ApplicationStateProviderProtocol, didReceiveRemoteNotification userInfo: [AnyHashable : Any], fetchCompletionHandler completionHandler: ((UIBackgroundFetchResult)->Void)?) {
…..

        switch application.applicationState {
        case .active:
            break
        case .background:
            break

…..
}

@roninopf
Copy link
Contributor

Hi @wujunyang, thanks for writing in; hmm, I'm trying to understand the full context of the linked code, but would you be able to file a ticket with your support rep? They may already have the answer you're looking for, and will also know to collect specific information for us to process; the ticket will then be tracked internally so we can schedule and allocate time to it.

In the mean time, I'll look in to this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants