V5.51 - Feedback

MacroDroidDev

Administrator
Staff member
Every version update adds some bugs to the Logcat Trigger. No update despite such an important trigger. Anyway, let's talk about bugs.
1) Some times when logcat trigger is opened app closes. Even if it can be opened again in the new macro md app closes , when open/add to the old macro.
2) After editing this trigger, editing it again creates a clone trigger. Enable/disable this clone trigger behaves the same.

But these bugs are not always seen.

Android 12

I have not touched the logcat trigger in a long time, so I think it's highly unlikely that I add a new bug to it every time. The reality is the LogCat trigger is flakey and unreliable and I wish I never added it given that it's basically blocked in the new versions of Android.
 

MacroDroidDev

Administrator
Staff member
Hi,

Since the last update, I’ve been experiencing an issue with app recognition, as shown in (screenshot 1.)

I’d also like to know if it’s possible to display a complete variable in the MacroDroid sidebar (screenshot 2).

For example, if I want to display the system log, it asks me for the maximum number of lines, but when displaying a variable, it only shows 2 lines, even though the variable is larger.
Sorry but I have no idea what screenshot 1 is supposed to show, or what issue you are referring to.

I will add a max lines option to variables in the side bar in a future update (but not in 5.51).

Please use report a bug in the troublehooting section so I can see if there are any crashes from your device.

I can't recreate the issue with the cloned trigger. If you know of a reliable way to recreate it please let me know.
 

Winny57

Active member
In capture 1 the problem is visible at the bottom in the green text with the ???

Normally this displays the application in the foreground and depending on the application in the foreground the system information (green text) is displayed or not displayed but the MacroDroid no longer detects the application in the foreground that's why it displays the ???
 

md_sgf

Well-known member
Do you think some macros need to be recreated?. Would that stop the crashing?
I meant in the context of having upgraded to 5.51.1. Maybe some old macros aren't been correctly read by updated macrodroid, so if I recreated those macros I am thinking I might be able to "fix" them?
 

md_sgf

Well-known member
Successfully downgraded back to 5.50.7 (y) (& didn't need to uninstall-->reinstall --> re-import! :cool:)
For those interested, I used usb + cmd: adb install -r -d <app pathname on computer>

Now I might upgrade to 5.50.10 (google play store). Unsure why you can only download apk up to 5.50.7 here ---> V5.50
 
Last edited:

md_sgf

Well-known member
"Successfully" upgraded to 5.50.10 (google play store).
However, now Floating Text action doesn't work. Including after restart. And that is a deal-breaker. Might have to uninstall-->reinstall? 🤔
 

SHAWON

Member
I have not touched the logcat trigger in a long time, so I think it's highly unlikely that I add a new bug to it every time. The reality is the LogCat trigger is flakey and unreliable and I wish I never added it given that it's basically blocked in the new versions of Android.
Adding Logcat to some macros causes the Macrodroid app to crash.
Can't fix this bug?
 

MacroDroidDev

Administrator
Staff member
Adding Logcat to some macros causes the Macrodroid app to crash.
Can't fix this bug?

I can fix the bug if I can recreate it or identify where it comes from, but currently I am not seeing any such crash. Please use report a bug in the troubleshooting section and then I can try and find your crash or alternatively give me some reproducible steps that will cause the crash and I will reproduce it that way.
 

MacroDroidDev

Administrator
Staff member
In capture 1 the problem is visible at the bottom in the green text with the ???

Normally this displays the application in the foreground and depending on the application in the foreground the system information (green text) is displayed or not displayed but the MacroDroid no longer detects the application in the foreground that's why it displays the ???
I don't see any issues with this. Please check that you have the standard MacroDroid accessibility service enabled, check your system log for any errors and if you still have issues use "Report a Bug" in the troubleshooting section.
 

md_sgf

Well-known member
"Successfully" upgraded to 5.50.10 (google play store).
However, now Floating Text action doesn't work. Including after restart. And that is a deal-breaker. Might have to uninstall-->reinstall? 🤔
Got Floating Text working again 😅🙏
MacroDroid 101.1 failed (restart)
MacroDroid 101.2a succeeded ("refreshed" via clear app data --> re-import .mdr)
MacroDroid 101.2b not required (uninstall-->reinstall; would have done next)
 

Endercraft

Moderator
Did anything change with the phone trigger in the latest release? I've just had a call incoming trigger fail, which has never happened (it was still working yesterday). No system updates either AFAIK.
 

GamBIT

Active member
Since MD 5.49.13 I see a trouble. MD is able to make some phantom copies of the variables, but broken. As the name for it is used a link like {v=name} and the value is empty.
If I save MDR with 5.49.12 and open it in 5.49.13-5.51.x then I can see at the global variables page these phantom variables. I can delete them and then save in 5.49.13+ , but if to open this resaved MDR again these variables appear again. Even they were deleted before saving.
The other related bug was - MD was using this variable instead of the real that was indicated in the action. But the log was showing that the phantom was used, with wring result. So the macro that was working well in 5.49 began to fail in 5.51.
I think MD has now some problem with variable ID (if it is really used inside MD). Maybe that is the reason for appearing those phantom broken copies for the proper real variables.
At 5.51 this problem does continue to be.
 

LinerSeven

Active member
Since MD 5.49.13 I see a trouble. MD is able to make some phantom copies of the variables, but broken. As the name for it is used a link like {v=name} and the value is empty.
If I save MDR with 5.49.12 and open it in 5.49.13-5.51.x then I can see at the global variables page these phantom variables. I can delete them and then save in 5.49.13+ , but if to open this resaved MDR again these variables appear again. Even they were deleted before saving.
The other related bug was - MD was using this variable instead of the real that was indicated in the action. But the log was showing that the phantom was used, with wring result. So the macro that was working well in 5.49 began to fail in 5.51.
I think MD has now some problem with variable ID (if it is really used inside MD). Maybe that is the reason for appearing those phantom broken copies for the proper real variables.
At 5.51 this problem does continue to be.
Hi, @GamBIT ,

>But the log was showing that the phantom was used, with wring result.

Could you share screen capture of what exactly is being logged on your device?

Regards,
Liner Seven,
 

dhj49er

Well-known member
Since MD 5.49.13 I see a trouble. MD is able to make some phantom copies of the variables, but broken. As the name for it is used a link like {v=name} and the value is empty.
If I save MDR with 5.49.12 and open it in 5.49.13-5.51.x then I can see at the global variables page these phantom variables. I can delete them and then save in 5.49.13+ , but if to open this resaved MDR again these variables appear again. Even they were deleted before saving.
The other related bug was - MD was using this variable instead of the real that was indicated in the action. But the log was showing that the phantom was used, with wring result. So the macro that was working well in 5.49 began to fail in 5.51.
I think MD has now some problem with variable ID (if it is really used inside MD). Maybe that is the reason for appearing those phantom broken copies for the proper real variables.
At 5.51 this problem does continue to be.
I don't see any phantom variables.

When does MD make the phantom variables?
You mention saving a macro in one version and opening it in a newer version - is this the only way phantom variables are generated?

For the above example does it generate phantom variables on every macro or only a few?

Is it just global variables or doe it include local variables?

Do macros saved in 5.49.12, deleted in 5.49.12 and then imported into 5.49.12 generate phantom variables?
 

GamBIT

Active member
I don't see any phantom variables.

When does MD make the phantom variables?
You mention saving a macro in one version and opening it in a newer version - is this the only way phantom variables are generated?

For the above example does it generate phantom variables on every macro or only a few?

Is it just global variables or doe it include local variables?

Do macros saved in 5.49.12, deleted in 5.49.12 and then imported into 5.49.12 generate phantom variables?
Firstly I have noticed this when updated from 5.49.13 to 5.51.3. One macro has become doing wrong, I've seen the new errors in log that the phantom string variable is wrong, while in the text of the macro was the proper variable. Right variable in macro, the different in log. Surprise of the updating.
I started to manage. I have seen that phantoms, deleted and saved (still in 5.53.3). Then deleted all in MD and reloaded that saving. All the phantoms were back at the places. I tried to load saving that done in 5.49.13 - 5.53.3 opened it with the bugs too. I have installed 5.49.12 and it could open saving in 5.49.13 without any phantoms. While 5.49.13 did open its own saving with the phantoms!
So, I can say that 5.49.12 is the last ver to open normally its savings.
Now I have changed smth to make that macro run as it must, in log I cannot see these errors, but 2 phantoms I cannot delete out of the savings in 5.49.13 and +. They are not used but appear after loading MDR, even if I delete them before.
I recall that many time I have a similar problem with one variable that isnt in any macro anymore but couldnt be deleted. It had appeared every time I deleted. Immortal :) Even when it seemed to be done successfully, later it appears again. Finally I began not to pay attention on it, but its worth to be deleted.
 
Last edited:
Top