Wechat applet subscription message development process

Preface

• Official account is divided into subscription number and service number ：
  The subscription number is daily 1 Time , But it will be hidden in the subscription column , There will be no digital notifications ;
  The service number is monthly 4 Time , You can have digital notifications like friend messages . In addition, there is a template message for the service number , It can be used for official account to send important service notices to users , The maximum daily call is 10 Ten thousand times .

• The message notification of the applet also has the subscription function ： Reference material
  One time subscription ： A call can be subscribed to at most 3 Bar message .
  Permanent subscription ： After the user subscribes once , Developers can send multiple messages over a long period of time . At present, long-term subscription information is only for government affairs and people's livelihood 、 Medical care 、 traffic 、 Finance 、 Education and other offline public services are open .

Environmental Science

• Wechat applet
• WeChat public platform
• JAVA The backend development

WeChat public platform

Login applet , Select subscribe message and subscribe

Then select a one-time subscription message （ Permanent subscription is not easy to apply ）. Be careful , When selecting a subscription message from the one-time subscription message template , The subscription message template you can search and see is related to the applet category you log in , The category setting position is shown in the figure below .

When you choose the right template , Put the template's ID To the back end , In addition, there is the detailed content field under the template . Here's the picture （ Click on my template -> details ）

Because my template is obtained through the back-end interface , So my template can be modified after it goes online ？ I haven't tried , But theoretically, it works .

JAVA

Because our backend needs to count the templates agreed by users , If you don't agree, don't send the notice . The options considered at that time were 2

1. The front end gets the results from the callback method of wechat and uploads them to the back end through the interface
2. The back end is directly connected to wechat , adopt Subscribe to message event push To obtain user authorization

Through the unremitting struggle of the front end （ Secondary reusability 、 Expansibility and reliability, etc., and sufficient deception ability ）, Decide to adopt the scheme 2. But there is a problem in the process of docking . Errors are always reported when submitting

In the development and management of small programs -> Development and setup -> Message push , When configuring information, put the file under the corresponding domain name as required, but it still fails . Asked about the background development , It is said that you have accepted the message push as required Post Method . Wechat has no detailed explanation in this regard , You can only go to Baidu Google to find experience .

I happened to see a tree planted by my predecessors in the same pit , At first glance, it looks cool , Hide ~

Wechat will send a get Request to do an authentication on the submitted server address , Indicates that the address is valid and legal . But our server only does post Message receiving request , Didn't do get request , Therefore, wechat authentication is not passed when submitting , It is understandable to report failure . Immediately notify the backend ~ Do it quickly , Sit back and wait for
After the back-end developers work overtime （ No signature verification , Go straight back to echostr, This field must be returned as is , Otherwise, the verification may fail due to the wrong type ） after , Configuration is successful ！
Test the following

Successfully configured

The back-end code is also attached
link : https://pan.baidu.com/s/1n9X6ss1jGqXvPn7zSyUJZg Extraction code : htc3