友盟推送api调用出现2027:签名不正确和2066:device_tokens长度非法

提个工单咨询一下友盟官方的技术官

签名：$url = https://msgapi.umeng.com/api/send?sign=9786afab006fabc76144175a9c871642

$post_data = "appkey":"","mipush":"true","mi_activity":"","timestamp":1654758274,"type":"unicast","device_tokens":"An93WSp4hMf7uUG6S80Q4s0_CGV1GLbCkEjc","alias_type":"id","alias":"ss1023","payload":{"display_type":"notification","body":{"ticker":"\u56de\u590d\u4ea4\u671f","title":"\u56de\u590d\u4ea4\u671f","text":"\u60a8\u67091\u4e2a\u56de\u590d\u4ea4\u671f\u901a\u77e5","after_open":"go_activity","activity":"com.xlkx.salesmanclient.activity.push.PushActivity"},"extra":{"status":"3"}},"policy":{"expire_time":"2022-06-09 15:09:34"}}

发送 ： curl( $url, $post_data)

测试结果： 还是报错签名不正确

device_tokens长度：安卓：44 ios：64 长度是合格的，还是报长度非法

先检查一下计算签名时使用的编码方式和发送时是否一致，此外，就经验来看，为保证加密成功，AppMasterSecret 应选择其对应的值，确保App MasterSecret设置正确。签名不正确是因为用户生成签名里的参数和发送消息的参数不一致，不要发送时参数encode，生成sign时用原始字符串，要保持一致。看一下请求的参数和签名用的参数是不是同一个字符串。device_token位数安卓：44 ios：64