V5.51 - Feedback

[MacroDroidDev]

For clear bugs, please use report a bug in troubleshooting section including the relevant macro (if relevant) with a clear description.

For other issue and discussions (related only to this beta), please leave all feedback here. Please keep discussion focused on this beta release and not general issues with MacroDroid as a whole.

 

[AkashiDom]

I'll be honest, this is so cool…

Spoiler: Cool Thing

 

[Endercraft]

The overlay bar action with show in status bar area ticked has the same effect as immersive mode. It's odd that the action that is supposed to do this doesn't work anymore.

 

[LinerSeven]

Hi, @MacroDroidDev,

I tried using Macrodroid v5.51.0 and checked out the fixes related to the new Tasker plugin.

In my environment, I tried recombining the pass-through variable specification (the leading %, previously required by the Tasker plugin) and it works, but at the same time it no longer catches the value of the variable on the Macrodroid side.

For example, KWGP case now looks like this:





Best Regards,
Liner Seven,

 

[MacroDroidDev]

The overlay bar action with show in status bar area ticked has the same effect as immersive mode. It's odd that the action that is supposed to do this doesn't work anymore.

I wasn't aware that it has stopped working to be honest, but I just tried it and you are correct, it no longer works and I can't find any simple replacement that does work.

The overlay bar is not the same as immersive mode, because MacroDroid is the foreground activity so it's easy to make full screen in this case. As soon as the foreground activity is removed the old state is restored.

 

[MacroDroidDev]

Hi, @MacroDroidDev,

I tried using Macrodroid v5.51.0 and checked out the fixes related to the new Tasker plugin.

In my environment, I tried recombining the pass-through variable specification (the leading %, previously required by the Tasker plugin) and it works, but at the same time it no longer catches the value of the variable on the Macrodroid side.



Best Regards,
Liner Seven,

Thanks for flagging this, I shall look into this now and try to fix for the next update.

 

[MacroDroidDev]

@LinerSeven I just looked at the KWGT plugin and it looks like it's quite complex and it's apparent that I don't really know what I'm doing with it. Is there a simple set of steps you can give me to set something up to reproduce the problem.

I'm not fully understanding what external_ip is in this case and how it maps to MacroDroid variables.

 

[LinerSeven]

@LinerSeven I just looked at the KWGT plugin and it looks like it's quite complex and it's apparent that I don't really know what I'm doing with it. Is there a simple set of steps you can give me to set something up to reproduce the problem.

I'm not fully understanding what external_ip is in this case and how it maps to MacroDroid variables.

Hi, @MacroDroidDev,

KWGT side as follows,









$br(tasker,valuable)$

 

[LinerSeven]

@MacroDroidDev ,

MD side as follows,







Regards,
Liner Seven,

 

[LinerSeven]

Sorry for all the images.

 

[MacroDroidDev]

Thanks @LinerSeven I have found the issue and it will be fixed in the next update. You will still need to use %valuable in this case. The pass through is really only relevant for Plugin developers who support both the trigger and the action as it allows data that is returned by the trigger to be silently passed through to the action call.

 

[LinerSeven]

Thanks @LinerSeven I have found the issue and it will be fixed in the next update. You will still need to use %valuable in this case. The pass through is really only relevant for Plugin developers who support both the trigger and the action as it allows data that is returned by the trigger to be silently passed through to the action call.

Hi, @MacroDroidDev ,

Thanks, this issue solved on my device MD 5.51.1.

Regards,

Liner Seven,

 

[Elieston]

I had a problem with the overlay bar action, when displaying the contents of a dictionary variable. The contents of this variable are very large and the action took up the entire screen and I was unable to remove the display from the screen because there was no clickable area outside the overlay bar. I had to restart the cell phone to get it back to normal.

 

[MacroDroidDev]

View attachment 12731I had a problem with the overlay bar action, when displaying the contents of a dictionary variable. The contents of this variable are very large and the action took up the entire screen and I was unable to remove the display from the screen because there was no clickable area outside the overlay bar. I had to restart the cell phone to get it back to normal.

That is a good point, that I hadn't considered. I shall give it some thought!

 

[Jacob L]

That is a good point, that I hadn't considered. I shall give it some thought!

If it is scrollable and a bit smaller it would create a clickable area or draggable to bin

 

[Winny57]

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.

 

[SHAWON]

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

 

[md_sgf]

The search is broken in 5.51.1.
It was working in 5.50.7.
It "works" if type: a,c,e,i,n,o,r,s,t
It doesn't work if type: b,d,f,g,h,j,k,l,m,p,q,u,v,w,x,y,z
(by working, I mean it shows down arrow, and highlights triggers, although garbage results)

Editor is unusable, as it often crashes when try to edit something. Well, that's what you get when trying betas - gotta take good with the bad. I really only upgraded so I could make a bug report (I should have upgraded to play store version). I think I'll need to downgrade back to 5.50.7 PRONTO!

 

[md_sgf]

1) Sometimes the app closes after opening it. Even if it can be opened again in the new macro, the app closes if it is opened in the old macro.

Do you think some macros need to be recreated?. Would that stop the crashing?

 

[SHAWON]

Do you think some macros need to be recreated?. Would that stop the crashing?

No, there is no need to recreate the macro because the problem is mainly in the logcat trigger. Adding a logcat trigger to some macros causes the app to crash.