V5.33 - Feedback

[MacroDroidDev]

For obvious bugs, please use report a bug in troubleshooting section with a clear description.

For other issue and discussions, please leave all feedback here.

 

[Endercraft]

This release is marked as an April release, as I anticipate it going live into production some time in April.

Version 5.33 (May 2023)

Yes it makes a lot of sense.
Should I edit it ?

 

[Jacob L]

Selection dialog is causing a crash for me

 

[Josué García]

Selection dialog is causing a crash for me

This happened for me too, but something very strange is that I chose to display from a dictionary and then it magically fixed itself and I couldn't recreate it anymore but it sure looks like a bug

 

[Dm114]

Great feature but unfortunately same as for @Jacob L with some details:
- manually defined entries => crash
- selecting existing array => crash
- selecting existing dictionary => ok but shows values [iterator_value] instead of value of each keys [iterator_dictionary_key].

 

[Dm114]

Great feature but unfortunately same as for @Jacob L with some details:
- manually defined entries => crash
- selecting existing array => crash
- selecting existing dictionary => ok but shows values [iterator_value] instead of value of each keys [iterator_dictionary_key].

When selecting an array (before it crashes), it's impossible to select the whole array: you must chose one of the indexes (it is OK for dictionaries).

 

[Endercraft]

Selection dialog is causing a crash for me

Same, except MacroDroid now does not want to start again. It keeps crashing

 

[Endercraft]

Nevermind I got saved. (still can't enable MacroDroid without crashing however)

The crashes stopped for whatever reason.

 

[MacroDroidDev]

Yes it makes a lot of sense.
Should I edit it ?

Selection dialog is causing a crash for me

I've identified this issue and have a fix ready for the next beta.

 

[MacroDroidDev]

Great feature but unfortunately same as for @Jacob L with some details:
- manually defined entries => crash
- selecting existing array => crash
- selecting existing dictionary => ok but shows values [iterator_value] instead of value of each keys [iterator_dictionary_key].

Just to be clear the intention is to show the values in a dictionary (not the keys) just as it shows the values in an array.

 

[MacroDroidDev]

When selecting an array (before it crashes), it's impossible to select the whole array: you must chose one of the indexes (it is OK for dictionaries).

Can you clarify exactly what you mean by this. I see the opposite issue, if I choose an array with sub-arrays I can only select the top level array (not sub-level items).

 

[Dm114]

Just to be clear the intention is to show the values in a dictionary (not the keys) just as it shows the values in an array.

Ok, I understand

 

[Dm114]

Can you clarify exactly what you mean by this. I see the opposite issue, if I choose an array with sub-arrays I can only select the top level array (not sub-level items).

You're probably right because I tested with a one-level array (and a multi-level dictionary).

 

[MacroDroidDev]

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

 

[Endercraft]

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

Let's just hope that MacroDroid doesn't crash again and set my battery to -infinite by auto-starting and crashing... Hopefully my 'auto disable MD in case of too many crashes' macro works as intended.

 

[MacroDroidDev]

Let's just hope that MacroDroid doesn't crash again and set my battery to -infinite by auto-starting and crashing... Hopefully my 'auto disable MD in case of too many crashes' macro works as intended.

In your case these sort of crashes are almost certainly due to the extreme number of macros you are running, as you have already mentioned you get lots of out of memory crashes and similar. I will be the first to admit that I never for a minute considered that people would run over 500+ macros and the app is not optimized well for this extreme use case. I have no idea how or why you need such an extreme setup, but in the short term to improve reliability I would suggest reducing the macro numbers down.

 

[Endercraft]

Talking about this all my macros got deleted (except the disable MacroDroid one) when it stopped crashing.... And I didn't notice until today.

You also have to consider that 1/3 of these macros are disabled (I don't have the exact number so this may be completely wrong).

 

[MacroDroidDev]

Can the encrypted macro be retrieved and read without encryption via the backup file?

Sorry, but I'm not sure what your question means. The encrypted export is a way to export your macros to share to prevent the macro file being tampered with before importing by someone else and to prevent someone importing who doesn't know the password.

 

[Endercraft]

In your case these sort of crashes are almost certainly due to the extreme number of macros you are running, as you have already mentioned you get lots of out of memory crashes and similar. I will be the first to admit that I never for a minute considered that people would run over 500+ macros and the app is not optimized well for this extreme use case. I have no idea how or why you need such an extreme setup, but in the short term to improve reliability I would suggest reducing the macro numbers down.

Maybe I should consider cleaning up my macros. It's a "complex mess"

 

[MacroDroidDev]

Maybe I should consider cleaning up my macros. It's a "complex mess"

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