Can push messages be distinguished between disabling notifications and uninstalling?

巴扎黑
Release: 2016-11-22 14:35:20
Original
924 people have browsed it

For message push, ios uses apns, and android uses gcm. If the push fails, an invalid token will be returned. However, among the invalid tokens, can we distinguish which ones are prohibited notifications and which ones are caused by uninstalling the app?

1 APNS PHP push return error handling
Push.php

if (!empty($aMessage['ERRORS'])) {
foreach($aMessage['ERRORS'] as $aError) {
if ($aError['statusCode'] == 0) {
$this->_log("INFO: Message ID {$k} {$sCustomIdentifier} has no error ({$aError['statusCode']}), removing from queue...");
$this->_removeMessageFromQueue($k);
continue 2;
} else if ($aError[&#39;statusCode&#39;] > 1 && $aError[&#39;statusCode&#39;] <= 8) {
$this->_log("WARNING: Message ID {$k} {$sCustomIdentifier} has an unrecoverable error ({$aError[&#39;statusCode&#39;]}), removing from queue without retrying...");
$this->_removeMessageFromQueue($k, true);
continue 2;
}
}
if (($nErrors = count($aMessage[&#39;ERRORS&#39;])) >= $this->_nSendRetryTimes) {
$this->_log(
"WARNING: Message ID {$k} {$sCustomIdentifier} has {$nErrors} errors, removing from queue..."
);
$this->_removeMessageFromQueue($k, true);
continue;
}
}
Copy after login

By disabling notifications, apns will not report an error and will not regard this token as an invalid or wrong token.

Uninstalling the app will call the following judgment, statusCode is equal to 8

 if ($aError[&#39;statusCode&#39;] > 1 && $aError[&#39;statusCode&#39;] <= 8) {
$this->_log("WARNING: Message ID {$k} {$sCustomIdentifier} has an unrecoverable error ({$aError[&#39;statusCode&#39;]}), removing from queue without retrying...");
$this->_removeMessageFromQueue($k, true);
continue 2;
}
Copy after login

Therefore, apns should be able to distinguish push failures caused by uninstallation, but disabling notifications will not respond

2 GCM error judgment code analysis:
Response.class .php

/**
     * Returns an array containing invalid registration ids
     * They must be removed from DB because the application was uninstalled from the device.
     *
     * @return array
     */
    public function getInvalidRegistrationIds()
    {
        if ($this->getFailureCount() == 0) {
            return array();
        }
        $filteredResults = array_filter($this->results,
            function($result) {
                return (isset($result[&#39;error&#39;]) 
                && (($result[&#39;error&#39;] == "NotRegistered")  || ($result[&#39;error&#39;] == "InvalidRegistration")));
            });
        return array_keys($filteredResults);
    }
    /**
     * Returns an array of registration ids for which you must resend a message (?),
     * cause devices aren&#39;t available now.
     *
     * @TODO: check if it be auto sended later
     *
     * @return array
     */
    public function getUnavailableRegistrationIds()
    {
        if ($this->getFailureCount() == 0) {
            return array();
        }
        $filteredResults = array_filter($this->results,
            function($result) {
                return (
                    isset($result[&#39;error&#39;])
                    &&
                    ($result[&#39;error&#39;] == "Unavailable")
                    );
            });
        return array_keys($filteredResults);
    }
Copy after login

If notifications are disabled, neither of the above two methods will write the error token. That is to say, if notifications are disabled, the token is also valid and no error will be returned.
If the app is uninstalled, getInvalidRegistrationIds will be executed, and $result['error']==NotRegistered

In this way, if GCM returns NotRegistered, it means that the error message is caused by uninstallation, and the notification is prohibited. GCM treats it as Normal tokens are issued.


Through the above test, it shows that apns and gcm handle ban notifications as normal tokens, while uninstalling the app will treat them as invalid tokens. (If you uninstall and reinstall, a new token will be generated)

Related labels:
source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template