Appcan-Push issues general log troubleshooting steps

Appcan Push Service Basic process

Step_1: Check if the network port is connected

• Check if the push server is connected to the APNS server port

  telnet gateway.push.apple.com 2195

  telnet feedback.push.apple.com 2196

• Check if your Android device is connected to a push server port on the network

  telnet mapp.zjtobacco.com 1883

  For example only, the specific Android push service port is configured in the app package-switch settings:

Step_2: Check app launch escalation and push device bindings are working

You need to monitor the push_in service Log on the push server (typically the Emmin node):

tail -f /data/log/mas/PUSH_IN.log | egrep "startUp|bindUserPush"

• When the application on the terminal device is launched and successfully escalated , the following logs are displayed:

• When the app logs in and completes the push device bindings , the following log is displayed:

Step_3: Publish push information from the EMM console and check that the push service is healthy

• Check that the EMM console's push task Publishing Service is working

  Specifically, monitor the push_admin service Log on the EMM console server (Emmweb node):

  tail -f /data/log/mas/PUSH_ADMIN.log

  When the push task is successfully published, the following log is displayed:

• Check if the push service is working

  It is necessary to detect the Push_service service Log on the push server (typically the Emmin node):

  tail -f /data/log/mas/PUSH_SERVICE.log | egrep "MQTT|APNS"

  When the push message is sent successfully , it is shown as follows:

  • Target device is Android device:

  • Target device is an iOS device:

  When the push message is successfully delivered , the following are shown:

  • Target device is Android device:

  • Target device is an iOS device:

Above, the complete troubleshooting process for releasing push tasks from the EMM console to a successful end-of-delivery device.

Appcan-Push issues general log troubleshooting steps