v5.50 - 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.

 

[Josué García]

The Display Dialog action has an extra magic text button.

 

[PentiumHAL9000]

I'm in trouble and don't know how to deal with this.

kotlin.UninitializedPropertyAccessException: lateinit
property uilnteractionResultCache has not been initialized at
com.arlosoft.macrodroid.action.UlInteractionAction
.q5(SourceFile:9) at
com.arlosoft.macrodroid.action.UllnteractionAction
$g$a.invokeSuspend(SourceFile:29) at
com.arlosoft.macrodroid.action.UlInteractionAction
$g$a.invoke(SourceFile:2) at
com.arlosoft.macrodroid.action.UlInteractionAction
$g$a.invoke(SourceFile:1) at yi.b.c(SourceFile:19)
at kotlinx.coroutines.x2.b(SourceFile:24) at
kotlinx.coroutines.x2.d(SourceFile:91) at
com.arlosoft.macrodroid.action.UlInteractionAction
Sg.invokeSuspend(SourceFile:50) at
kotlin.coroutines.jvm.internal.a.resumeWith(Source
File:12) at
kotlinx.coroutines.u0.run(SourceFile:129) at
zi.a.P(SourceFile:1) at zi.a$c.d(SourceFile:15) at
zi.a$c.p(SourceFile:29) at zi.a$c.run(SourceFile:1)
Suppressed:
kotlinx.coroutines.internal.DiagnosticCoroutineCont
extException: [m2(Cancelling)@513846b,
Dispatchers.Default]

 

[PentiumHAL9000]

MacroDroid crashes when opening a macro that uses a content ID in UI screen operations

 

[Endercraft]

I'm in trouble and don't know how to deal with this.

kotlin.UninitializedPropertyAccessException: lateinit
property uilnteractionResultCache has not been initialized at
com.arlosoft.macrodroid.action.UlInteractionAction
.q5(SourceFile:9) at
com.arlosoft.macrodroid.action.UllnteractionAction
$g$a.invokeSuspend(SourceFile:29) at
com.arlosoft.macrodroid.action.UlInteractionAction
$g$a.invoke(SourceFile:2) at
com.arlosoft.macrodroid.action.UlInteractionAction
$g$a.invoke(SourceFile:1) at yi.b.c(SourceFile:19)
at kotlinx.coroutines.x2.b(SourceFile:24) at
kotlinx.coroutines.x2.d(SourceFile:91) at
com.arlosoft.macrodroid.action.UlInteractionAction
Sg.invokeSuspend(SourceFile:50) at
kotlin.coroutines.jvm.internal.a.resumeWith(Source
File:12) at
kotlinx.coroutines.u0.run(SourceFile:129) at
zi.a.P(SourceFile:1) at zi.a$c.d(SourceFile:15) at
zi.a$c.p(SourceFile:29) at zi.a$c.run(SourceFile:1)
Suppressed:
kotlinx.coroutines.internal.DiagnosticCoroutineCont
extException: [m2(Cancelling)@513846b,
Dispatchers.Default]

Please use the report bug button in the troubleshooting section of the app. If you can't use the app to send it, directly email support@macrodroid.com.

 

[Endercraft]

Fixed issue where floating text could flash when regularly updating existing floating text

I always thought this was something that was unavoidable and caused by whatever is used to draw floating texts... That's nice!

 

[MacroDroidDev]

As a general comment, I've seen quite a few unexplained crashes in v5.50. It looks like some kind of build level issue or similar because there are multiple unexplainable issue. It may be wise to wait before intalling 5.50 until the .1 release it out if you are considering it.

 

[dhj49er]

Tried to submit a bug with the attached screenshot but the report failed to complete. This happened twice. Showing here in case it's useful..
The macro show refresh rate appeared to run ok, but the system log shows multiple errors

 

[Josué García]

The template store does not load and fills the log with this error.

 

[dhj49er]

The template store does not load and fills the log with this error.

I'm not sure I understand your comment.
When is the template store invoked?
I see these errors when some macros are run.

 

[MacroDroidDev]

@dhj49er I don't think @Josué García report was related to yours, he is just saying for him the template store is not working and there are errors (similar to yours) in the system log.

At the moment I am not seeing these same errors, so it's going to take some investigation to work out what is going on here.

 

[MacroDroidDev]

Now I have managed to recreate these issues on a device, so now I just need to figure out why this is happening. Hopefully I will get to the bottom of this today and will put a new release out when I have solved it.

 

[MacroDroidDev]

I've just posted a new version which hopefully stop the spurios issues that seemed to happen on v5.50.0

 

[dhj49er]

I've just posted a new version which hopefully stop the spurios issues that seemed to happen on v5.50.0

After a few hours of using v5.50.1, I can confirm no spurious log entries have been generated.

Thank you @MacroDroidDev.

 

[MacroDroidDev]

After a few hours of using v5.50.1, I can confirm no spurious log entries have been generated.

Thank you @MacroDroidDev.

Great news, thanks for testing!

 

[GamBIT]

I have noticed in 5.49.13 (and in 5.50 most likely too) a situation when I have cloned a macro and it hasnt appeared in the macro list. I did it several times, the macros were really cloned, but nothing was shown till I have closed MD as an app and reloaded it again. Then those macros were shown.
I cannot say how to recreate this but Dev may keep it in mind if looking into a code at that part.

 

[huashimacro]

Dear developers, hello. After waiting for the trigger action to time out, the timeout status is saved to a boolean variable. Once set, save the macro. Then, export it by sharing the macro or by exporting a backup, and re-import the macro or the backup file. The configuration information for the 'wait until trigger action times out' status saved to the boolean variable in the macro file will be lost. I have observed this issue using version 5.50.1, and it still exists! This issue has been around for over a year without anyone addressing it. It might have slipped your notice due to your busy schedules. Recently, when using this action to write macros, the issue of the timeout status variable settings being lost after sharing is very troubling to me. I have to reset the variables every time. I hope this can be resolved! Thank you,developers ⌯oᴗo⌯ You are the best also, under the variable a dictionary, the 1 dictionary or 2 array saves the macro. If after setting the variable and running the macro, it feels unsuitable, delete the 1 dictionary and 2 array under the a dictionary to adjust the 1 dictionary under the a dictionary to an array type, and change the 2 array to a 2 dictionary type, then save the macro, and share or export the macro backup. This setting will also be lost. Here, a, 1, and 2 are all dictionary key names. When you import the macro file again, the variables under the a dictionary will be the same as the first time you set the variable type. As long as the key name is not changed, changing the dictionary type and saving it will result in the loss of the configuration when sharing, which is also very troubling for me and causes me to rewrite the macro file every time without daring to change the variable type within the dictionary Could you please also check this issue of the dictionary type change configuration being lost when saving and sharing in the variable dictionary? Thank you very much!

 

[Chunkycookie88]

Macro crashes when trying to sign in with email from google

 

[Endercraft]

@huashimacro @Chunkycookie88

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

 

[MacroDroidDev]

I just want to re-iterate that this thread is for the beta release specific issues only. PLEASE DO NOT report issues that are years old or relevant in older versions of the app. As soon as this starts happening the thread gets out of control turns into many pages of discussion and I cannot track the latest beta release issues easily. Please do as @Endercraft suggests and use the report a bug mechanism in the troubleshooting section of the app. If you can't do this for some specific reason then please post a thread on the help and troubleshooting board or email directly at support@macrodroid.com.

I am not going to reply to any issues raised here that are standard bugs within previous versions of the app so please report bugs as requested.