1. Airship Support
  2. Community
  3. iOS SDK

iOS App is waking up on background even if user did not clicked push

Avatar
archana patchirajan

Hi,

I sent a push notification specific to all users of my iOS app.

In the message details page, i can see only 174 as direct influence, and influenced users also less than 100, but if i check my server logs, i can see API calls from more than 1000 user.

It seems that app is waking up and hence, app is calling our service calls in the background for some users.

We have more than 60K users, and only 174 people are opened app, and influenced users also less than 100, but how come we get 1000 calls?

We have not enabled background processing also.

I am using UrbanAirship-iOS-SDK (12.1.2).

Please advise that how can avoid this awake of iOS apps.

Thank you.

Didn't find what you were looking for?

New post

Comments

3 comments

Sort by Date Votes
  • Avatar
    Chilun Liu

    Hello Archana,

    May I ask if you can forward your question to support@airship.com along with the following information so we can look into this?

    Thank you and regards,

    Airship Support

    Chilun Liu

    Comment actions Permalink
    0
  • Avatar
    dsdas VCVDSE

    When an iOS app wakes up in the background even if the user has not clicked on a push notification, this behavior typically results from background processes or tasks that the app is permitted to execute under specific conditions. Push notifications with a payload that includes the content-available: 1 flag trigger a background fetch, allowing the app to wake up and perform actions, such as syncing data. This is often used for updating content silently or preparing the app Alight Motion Full-Screen Ratio for a more seamless experience when the user next opens it.

     

    Comment actions Permalink
    0
  • Avatar
    dsdas VCVDSE

    When an iOS app wakes up in the background without the user interacting with a push notification, it often occurs due to the app's use of background modes or specific behaviors triggered by the push notification payload. In particular, notifications with the content-available key set to 1 can silently wake the app for background tasks like fetching data or updating content. This is common in apps that provide real-time updates or need to sync data periodically. Developers should carefully manage these wake-ups to ensure they align with Apple's guidelines to avoid excessive battery usage fixmyspeaker or unnecessary app launches. Debugging tools like the Background Fetch Logs in Xcode can help identify unintended background activity.

    Comment actions Permalink
    0

Please sign in to leave a comment.