5.49.5 version new issue! The variable change trigger does not fire; it only triggers when manually tested. I wrote a macro for an HTTP request push notification, which acquires the response by looping through the IP host address to open the website via HTTP. Then, it captures the receiver's IP address by responding to the receiver's HTTP request trigger and stores it in a variable named "new" on the current phone. This is used to push information to another phone using the HTTP request feature. (Two phones, A and B, are required; install this macro file on both phones A and B. Phone A turns on mobile data and creates a hotspot, while phone B connects to A's hotspot. The test for phone A's HTTP request to phone B's IP response is all normal. When testing phone B's request to phone A, there is a value echoed in the IP response, but the variable change trigger does not work. The log list already shows the response value echoed from phone A, yet the variable change trigger will not fire. However, when manually testing the trigger to run the macro, the variable change trigger can only be activated after the specified variable has been changed to the new value.)
I can't figure out where the problem lies. Is it a bug in the variable change trigger or an issue with my macro?
As shown in the video, it's a bit long at 9 minutes, and the software language is set to English.
After some research, I've found that: The HTTP page opening response receives the IP returned by the HTTP request, but the variable change trigger that is supposed to fire after the response value changes does not trigger. This is because the loop action list also uses the variable change trigger. By switching to a different trigger, the "new" variable can normally obtain the returned IP value. It seems that using multiple variable change triggers may cause some kind of conflict. Please, developers, verify and investigate the cause.