I didn't get my push notification or cell phone alert from my app?

Although enabling push notifications through our mobile app is the fastest and most convenient way to receive your trade alerts, there may inevitably be times when you do not receive an alert across your screen.

If you are having trouble with notifications, here are some of the most common reasons, and their subsequent fixes:

General Fixes Regardless of Device:

  • This may seem obvious, but we need to mention it. Please double check that you have notifications enabled in both the app AND your device's settings. Be sure to choose to have them show on your lock screen.
  • If you have no service, are in an area with spotty service, or have a bad connection; your notification may show up in the notification history tab in the app, but may not pop up on your screen. This is common among all notifications, and not a problem with Wanderer notifications specifically.
  • If your local network is experiencing difficulties, delivery may be interrupted, appear late, or not be delivered at all. This usually resolves itself once your network is restored to proper working order.
  • Sometimes, your phone simply needs a restart. Close the app and restart your phone. You'd be surprised how often this fixes this problem.
  • If you do not have a network connection, you will not receive a notification until a network connection is made. You have three days to do this.
  • Some home and commercial wifi routers will cause notification delivery delays. This is true for both iOS and Android devices.

iOS Specific Issues:

  • Go to your Settings>General>Background App Refresh. Be sure that Background App Refresh is enabled for the Wanderer App.
  • Although our stats show a near 100% delivery rate to apple devices. We are not in control of WHEN and exactly HOW you receive the notification. It is important to note that with iOS devices, our push notifications are sent to Apple Push Notification Service (APNS) which is based on Apple Servers. From there, they are delivered to your device, and Apple doesn't give any guarantee on successful message delivery. If Apple is experiencing heavy volume or a glitch in their system, your notification may be delayed.
  • When sending notifications to a device build with a development provisioning profile, Apple's APNS servers may sometimes be less fast or reliable. You can compare a version of your app built with an AdHoc provisioning profile and a production push certificate to see if it works better. In the near future, Apple will be changing the way this system works so this problem will go away.
  • Notifications may be delayed if "Restrict background data" is checked for the app, if Wifi-Optimization is turned on in the advanced settings, or if priority mode is enabled.

Android Specific Issues:

  • On many Android devices, if you force stop or force close the app from Settings>Apps or with a 3rd party task manager that uses the same method, then notifications will not be received until you open the app again or restart the device. 
  • Long pressing the back button on some devices force closes the app, and therefore disables notifications until the app is rebooted. (see above)
  • Using a 3rd party task killer like Greenify force closes the app and notifications will not be received (as stated above).
  • On some Android devices, your device will force stop certain apps to free up ram via the task manager. If this is the case, you won't receive notifications again until you reopen the app.
  • Swiping away your app while remote debugging it will stop notifications from being received. (Not a likely cause for most Wanderer users, but we'd be remiss if we didn't include it just in case.)
  • If none of these common fixes solve your Android issue, read this article from our Push Notification developer that lists specific information, bugs, and their subsequent fixes that device manufactures build into their Android phones that interfere with notification delivery. 
  • Some home and commercial wifi routers will cause the device's connection to Google's FCM/GCM servers to be closed. The device later re-opens the connection and receives the delayed notifications. (Discussed here: https://groups.google.com/forum/#!topic/android-gcm/Y33c9ib54jY)
  • Some custom versions of the Android OS have a power-saving setting that can cause notifications to be delayed or ignored. For instance, Sony Xperia devices have a "Stamina Mode". (Discussed here: https://talk.sonymobile.com/t5/Xperia-Z3-Compact/Notifications-not-Working-When-Phone-in-Sleep-Mode/td-p/879641)
  • Some Android devices can enter a low power mode when their battery is low that may cause slight delays in receiving notifications.
  • WhatsApp has a good list of instructions on troubleshooting delayed Android and iOS notifications here: https://www.whatsapp.com/faq/en/android/20887936

As always, we work hard to deliver the best possible experience to all of our subscribers. If you've tried ALL of the fixes above without success, contact us.

Still need help? Contact Us Contact Us