Can somebody help me?

[davisgodoy]

before the update I did not have this message in the registry and now it appears ... what can be the problem?

 

[davisgodoy]

antes de la actualización no tenía este mensaje en el registro y ahora aparece ... ¿cuál puede ser el problema?

el problema parece provenir de la misma aplicación que no reconoce el disparador. Esta es una macro simple que genera el error

 

[davisgodoy]

@MacroDroidDev

 

[tanutanu]

check the regex in your macro as the log. The pattern "(?s)" might be wrong. If you want to exclude white space, you need to use escape character like \s. And single ? doesn't accept in the capture group (). ?=, ?: and ?! are acceptable.

 

[davisgodoy]

the problem seems to be from the same app that is not recognizing the trigger. This is a simple macro that generates the error.

This is the macro that I am testing that in the previous version this message did not appear and now it does ..... it is a trigger that contains this expression *N300

 

[tanutanu]

Gotcha. It seems a bug.

 

[Josué García]

antes de la actualización no tenía este mensaje en el registro y ahora aparece ... ¿cuál puede ser el problema?

The error is your expression, use \*N300
It seems that your native language is Spanish.

El error es tu expresión, utiliza \* N300

 

[davisgodoy]

The error is your expression, use \*N300
It seems that your native language is Spanish.

El error es tu expresión, utiliza \* N300

add the character \ and the trigger is not activated ... it does not work ... it reiterated that in the previous version I did not see this error message and now in the new update it began to appear

 

[tanutanu]

oops, he means * as just a star in phone number
Actually, there's no letter in the pattern. I missed it. Thanks Josue.

 

[davisgodoy]

oops, he means * as just a star in phone number
Actually, there's no letter in the pattern. I missed it. Thanks Josue.

apparently the trigger is not recognizing the wildcard *

 

[davisgodoy]

apparently the trigger is not recognizing the wildcard *

@

before the update I did not have this message in the registry and now it appears ... what can be the problem?

@MacroDroidDev the problem arises when the check to enable the match is activated and at the same time the wildcard * is assigned, why when I remove the check it works like the previous version

 

[tanutanu]

apparently the trigger is not recognizing the wildcard *

Sorry, I'm not sure what you want to much.
if regex and match to any string longer than zero length, you have to add "." and it should be ".*N300"
if unix(android) shell style pattern matching, the wildcard(*) should be working correctly. Therefore it has a possibility to be a bug. However, I'm not sure when it was configured with "contains" option(as you ticked the checkbox). I confirm it works with "matched" option coz I always use that.
if just a part of string what you expect to the notification, you need to add backslash(\) as Josue told.

 

[tanutanu]

@

@MacroDroidDev the problem arises when the check to enable the match is activated and at the same time the wildcard * is assigned, why when I remove the check it works like the previous version

It is not correct regexp. see above my comment. * is different than simple wildcard in regular expression.

 

[davisgodoy]

Sorry, I'm not sure what you want to much.
if regex and match to any string longer than zero length, you have to add "." and it should be ".*N300"
if unix(android) shell style pattern matching, the wildcard(*) should be working correctly. Therefore it has a possibility to be a bug. However, I'm not sure when it was configured with "contains" option(as you ticked the checkbox). I confirm it works with "matched" option coz I always use that.
if just a part of string what you expect to the notification, you need to add backslash(\) as Josue told.

I have been using macros for 6 months and I did not present that error as I had been doing but now after the last update that error began to appear, which seems strange to me ... if before it worked well and now it does not ... .. In summary, what I do there is that I read only the notifications that contain, for example, the word N300 and that ends in Smart ..... Example: Unit N300 Stopped 20 Minutes Smart

 

[tanutanu]

I have been using macros for 6 months and I did not present that error as I had been doing but now after the last update that error began to appear, which seems strange to me ... if before it worked well and now it does not ... .. In summary, what I do there is that I read only the notifications that contain, for example, the word N300 and that ends in Smart ..... Example: Unit N300 Stopped 20 Minutes Smart

Previous wildcard behavior might be slightly inaccurate if you didn't change the option at all. I think it works correctly right now.

with regexp: .*N300.*Smart$
with wildcard: *N300*Smart
This is difference between regex and wildcard. It matches the same string like your example.
I always use ".+" instead of ".*" to avoid matching zero length string when I write in regexp.

 

[davisgodoy]

Previous wildcard behavior might be slightly inaccurate if you didn't change the option at all. I think it works correctly right now.

with regexp: .*N300.*Smart$
with wildcard: *N300*Smart
This is difference between regex and wildcard. It matches the same string like your example.
I always use ".+" instead of ".*" to avoid matching zero length string when I write in regexp.

I have always used the wildcard: * N300 * Smart and everything fine until the last update but now I get an error with that wildcard ... can you verify by placing that wildcard and activating the check of Enable matches and have the last update please?

 

[tanutanu]

I have always used the wildcard: * N300 * Smart and everything fine until the last update but now I get an error with that wildcard ... can you verify by placing that wildcard and activating the check of Enable matches and have the last update please?

Well, most important thing is that you recognize how to set your macro up currently.
I believe both works correctly, Please check your macro as the attached images. Pay attention to the difference of expressions in both screenshots as well.