V5.33 - Feedback

[Endercraft]

I would certainly recommend this, as I can rarely recreate any of the issues you report to me

I will soon when I have time

 

[Endercraft]

I have no idea how or why you need such an extreme setup

Half my macros are test macros that will probably never activate again. The real problem is some of my testing causes very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very weird issues to MacroDroid which doesn't seem to appreciate that a lot. Of course the number of macros is also a factor in this (25mb backups are not a great thing).

 

[dhj49er]

I've tried using encryption on output file when exporting a macro set and not sure it's working correctly.
I have a simple macro with 1 action - export macros.
When I edit the action and tick the encryption box and save the macro, then next time I edit the action the encryption box is unticked. I was expecting the setting to be remembered.

Have other users noticed the same issue?

Also trying to import an "encrypted" macro set, MD doesn't prompt for the password, before the overwrite warning.
That might be because the file hasn't been encrypted or the prompt is after the overwrite warning.

The export macros action doesn't provide the option to input a password. I have assumed it's the same password I have set for the Security category.

I have tried the above without entering my password and with entering the password by opening the security category, but the results in both cases are as stated above.

 

[MacroDroidDev]

@dhj49er It's definitely true that the export option does not remember the entered password and it would probably be nice if it at least remembered that you had used this last time and enabled the encryption option.

It's also true that the export macros action does not offer the ability to encrypt at this stage, however it's certainly something that will be possible to add later. At the moment it should simply not be encrypting the file as before, are you seeing something different?

 

[dhj49er]

....At the moment it should simply not be encrypting the file as before, are you seeing something different?

Thank you for the clarification.

As far as I can tell the export macro action is performing the same as before.

I haven't tried importing a macro set, as I haven't needed to do it, but from what I've seen it's the same as before.

 

[bennett]

Will it be possible to have an array of dictionaries with three keys, and populate all of the dictionaries's ”Name” value in the Selection Dialog?
I'm updating my Wake on LAN macro to support multiple defined devices.

 

[Dm114]

Thanks all for testing so far, I will put out a new beta tomorrow that should hopefully fix selection dialog issues.

MD v5.33.3 seems to work fine at least for Selection dialog.

 

[Endercraft]

That's 127 macros gone already. I made a backup before just in case. I hope I will be able to reach a level where MacroDroid won't get into such a weird state.

Edit : I reached 202 (having *only* 72 macros in 'Uncategorized' feels weird).

 

[MacroDroidDev]

Will it be possible to have an array of dictionaries with three keys, and populate all of the dictionaries's ”Name” value in the Selection Dialog?
I'm updating my Wake on LAN macro to support multiple defined devices.View attachment 5411

Not directly but you could probably parse the nested dictionary into a single dictionary and use that to display the values.

 

[dhj49er]

I've just installed 53.3.3 beta and I'm having issues, which only started after the installation.

Only a few macros run.
MD doesn't run macros on screen on or off.
MD doesn't respond to WiFi connections and disconnections.
The airplane on/off action doesn't work.
The ADB shell commands run but don't do anything.

I have tried clearing the MD cache followed by phone reset, but the issues persist.

Force stopping MD is unavailable from the app system settings

I cannot install a previous beta....package is invalid.

Is there anything else I can try before uninstalling and reinstalling MD?

See SOLVED below.

 

[Endercraft]

I've just installed 53.3.3 beta and I'm having issues, which only started after the installation.

Only a few macros run.
MD doesn't run macros on screen on or off.
MD doesn't respond to WiFi connections and disconnections.
The airplane on/off action doesn't work.
The ADB shell commands run but don't do anything.

I have tried clearing the MD cache followed by phone reset, but the issues persist.

Force stopping MD is unavailable from the app system settings

I cannot install a previous beta....package is invalid.

Is there anything else I can try before uninstalling and reinstalling MD?

I updated to v5.33 some days ago and I don’t think I will be updating back to v5.33 until a fix or 5.34. I‘m staying on v5.32.6 for now.

 

[dhj49er]

SOLVED

I toggled accessibility settings and MD sprang to life.

All the macros are working now.

On this phone, until today I haven't needed to toggle accessibility settings for months, so had forgotten all about the setting.

 

[dhj49er]

Unexpected behaviour of system log level setting.

I have used standard level setting with everything ticked and enabled except for Constraints for years. I enable Constraints when I develop a macro that's no working properly.
It worked as expected, importantly always retaining the standard level setting.

Now the standard level setting is not retained. Whenever I open the logging level setting screen the logging level has changed to detail. I can change it back to standard. However when I re-open the system log after closing it, it has changed to detailed.

Now if I tick Constraints and repeat the above test, the logging level changes from standard to debug.

In all cases the logging level doesn't change again if I just open or close the system log.

So once it changed from standard to either detailed or debug it will remain in detailed or debug.

I haven't seen this behaviour before.

Have other users noticed this or similar behaviour?

Is this the expected behaviour or a bug?

 

[MacroDroidDev]

@dhj49er Apologies this is a bug. The debug view should not be visible to users as it's only designed for very specific debug messages that are useful to me. I allowed it temporarily on a release build to debug something and forgot to disable it I guess!

 

[Endercraft]

The debug view should not be visible to users as it's only designed for very specific debug messages that are useful to me

You mean the detailed view shouldn't be available to us ? Could you make it stay somewhere in the settings to enable (like developer options) I find it useful too

 

[MacroDroidDev]

The detailed view is available to users. The "debug" view should not be.

 

[Endercraft]

The detailed view is available to users. The "debug" view should not be.

I saw this after updating. Except for the startup time I indeed don't see what could be useful to normal users.

 

[dhj49er]

Confirmation that the latest beta, 5.33.4, has resolved the system log level issues.

 

[LpmitBenjamin]

it seems that "identify in the application" doesn't work, at least he doesn't click on the ID (Home Screen, Back, Last opened) in version 5.33.4

 

[Endercraft]

Fixed minor issues on user page in the template store.

You mean the special [B][COLOR=rgb(124, 112, 107)]e[/COLOR][/B]ffect[COLOR=rgb(71, 85, 119)]s[/COLOR] ?
What just happened above even if it describes the issue I guess