When App not running no notification received

[Mohammad Al-mouallem]

For testing purposes we set the cool down period to 0 then we started testing with 2 beacons for about 10 notifications the results were so good each time the app get into beacon range notification is sent but after few notifications the app stopped receive any notification at all.

We found out the reason is because we killed the app if the app running the notifications are normally sent if we kill it no notifications.

Any idea why we got this behavior !

[Mark van der Tol]

Hi,

I presume you are talking about Android. When you kill an app on Android through the settings menu, it first has to be started again by the user. This is how Android is designed.

If the app gets killed by other means, for example when the device needs memory for some other processes or when the device is restarted, it works fine.

Kind regards,

Mark van der Tol

Plot Projects

[Mohammad Al-mouallem]

Hi,

No, we currently test on IOS9.

[Mark van der Tol]

Hi Mohammad,

After killing the app Plot should continue working. Most notifications we sent for our customers are sent when the app is in the background. I'm not sure what went wrong in your case.

For it to trigger it is possible you first have to get completely out of range of your beacons before a new one triggers after you've just killed your app. Also triggering a lot of notifications in a short period from the background is limited on iOS. This is a limitation of iOS. For most use cases this isn't a problem, since the end user just moves into an area and then just receives one notification.

Kind regards,

Mark van der Tol

Plot Projects

[Mohammad Al-mouallem]

Hi Mark, 

Thank you for your response however let me tell you about our app state.

First its been 2 days the app never got any notification we did get out of the beacon range multiple  times 

Second we just made a basic integration and it seems working since we receive notification normally when the app is running.

Please let me know if i can offer any information to get over this issue we have no clue what is the cause for this behaviour. 

[Mohammad Al-mouallem]

just thinking of your answer i would like to clarify something the notification received in both condition foreground and background but when app is killed no notification received. 

[Mark van der Tol]

I'm not sure what exactly goes wrong in your case.

Is it for newly created notifications or is also the case for notifications that exist for a longer period of time? It could be that these new notifications haven't synced yet.

[Mohammad Al-mouallem]

Hi Mark.

i do not think it is a sync issue since the notification created one week ago and its loaded in the app as i checked with  

loadedNotifications

  function.

For me i still get the regular notification when app is killed but not location based notification. ill try with new cordova app but, can you confirm that Plot plugin works when app is killed and not in the background !

Best Regards,

[Mohammad Al-mouallem]

Hi Mark,

You were right it works fine it just not triggering notification every time device enter a Beacon range. it takes time you said it is IOS limitation but, i want to ask 

• If it is push notification why there is such limitation ? we send a lot of push notification using our push service all of the notifications are received even when the app is killed and not running at all basically this the idea behind the push.
  
• Another question, when interacting with geofence , beacon plot trigger push or local notification ! because we still can't understand the limitation of send pushs because then cool down period make no sense because the app any way wont receive multiple push after each other.
• Last question is why there is delay triggering the notification for example if i set on exit trigger notification ill receive the notification after i walk abit away from the store.