Search results

For obvious bugs, please use report a bug in troubleshooting section with a clear description. For other issue and discussions (related only to this beta), please leave all feedback here.

V5.44.0 ===== Arm64 APK should work for most modern devices: https://macrodroidlink.com/beta/macrodroid_v5_44_0_beta-arm64.apk The universal APK is a larger download but should work on all devices. https://macrodroidlink.com/beta/macrodroid_v5_44_0_beta-universal.apk

This won't be available on the Play Store for the forseeable future until I can resolve the policy issue currently blocking my new releases. Version 5.44 (May 2024) ================ Added HTTP Server trigger and HTTP Server Response action. Added Speaking Text constraint. Added Text Shared...

I've already made another video and submitted another try which shows this so I'm waiting on the next rejection. The fact that it's guess work and you can't get any real human response that isn't a generic "it doesn't adhere to the policy" type email is pathetic.

Of course, this doesn't actually work it's just an endless unable to take a call 'Please try again later' .....

It's not viable from a business point of view I'm afraid.

If possible please upvote here: to get more visibility

Apparently I can get a call from someone at Google Play, so I'm just waiting for business hours to open for this......

So I submitted a video and updated my policy declaration to link to it: with full steps on how to use the app to do the same and it has been rejected again. The video you submitted does not demonstrate the functionality necessary to verify and approve your use case declaration (for example, if...

Sorry but I have not received any bug report from you and the video link you have posted does not work.

Yes you are quite correct, that is bad and the name when configured should indicate if enable or disable is selected. I will correct this soon.

In the side menu of the home screen you will see the troubleshooting section and the report a bug button is in there.

Please use report a bug in the trouble shooting section and include the relevant macro in the bug report.

I'm creating a YouTube video which shows an SMS automation being created and adding that to the policy form. Hopefully Mr Google Bot will be able to watch and enjoy the video and be convinced that an automation app can automate things, what could go wrong?

Wow I got a quick (no doubt automated appeal response): Unable to verify core functionality of app When you submitted your app, you specified your app's core functionality as follows: Device Automation. However, we couldn’t find evidence that the app offers the declared core functionality...

Once again an app update has been rejected due to the useless incompetence of the Google Play store review process. This time it's supposedly breaching the Policy Declaration for SMS/Call Log access because it's not a core feature of my app. However the particular funny thing is that they have...

Sorry it's more a case of Wear OS is a waste of my time because hardly anyone uses it, it's a pain to develop for as they keep changing everything and the app gets thrown off the store every 2 months for some new reason that they just made up. I don't wish to invest in the platform because...

I can't recreate this problem on any device I have tried I'm afraid and I don't know what could be the cause to be honest.

I see the "shell script timeout" message happening on my device when I clean install the helper file but don't launch and configure it. Once I have launched the helper app and disabled battery optimization etc. the problem goes away. Does the action actually work? What do you see in the log of...

I always refund users who have genuine reason and ask politely. If someone takes the mickey, like asking for a refund after a few years or they are abusive in any way then I will tend to decline the request.