2
Completed

Suggest autoapps have a setting for which account should be used when unlocking plugins to avoid it randomly picking an account and the tasks consistently failing to run.

No matter if the correct Google account is the first one logged in or if it's the last one logged in auto apps always chooses a random account to try and unlock my plugins. So basically none of my tasks run without hours of resetting up my phone each and every day. Yes I have read the faqs. My suggestion is to have auto apps ask the user which account to use for logging in plugins one time and always use that account or you could even have it ask upon each purchase which account to use and then you could have plugins you have purchased on different accounts all still work simultaneously together but that is a little forward thinking of me. My main goal here is to avoid this random account being signed into when unlocking a plugin. At its most basic ther should be  a setting or a O e time choice by the user of which account should be used. If you don't want to leave it to the user then use the account that autoapos is installed from. See the jao you made me have another idea about it. I still think it should be a setting for the user to pick an account but using the account that auto apps is installed from would still stabilize and lock it down to one account. I know auto apps can tell because it changes which apps are highlighted inside the app depending on which Google account its trying to use at the moment. Either way as it stands the app is basically unusable most of the time because every time I try to run an action it randomly picks a different account to use to unlock my plugins sometimes it chooses different accounts for 2 plugins in the same task. If Google won't fix thier s**t you have to work around it somehow. 

3 replies

W

dont ask them to do what you can do better.  

W

what do you mean they don't allow it.  You run the most customizable automation racket there is on android.  Im gonna say this and you can scoff at it if you want.  im gonna assume you mean that they don't have an api or set way to login to thier system as a third party app.  not that they will remove your app from the play store if billy bob types his password in and they don't like the keyboard he is using.  So save the user name that the client prefers to use as an array of characters or an encrypted png stored as one of taskers icons if don't really care. Password too. I would save them seperatly but thats just me.  And when auto apps goes to check your lisence or key or what ever it does when it activates an app. just erase that handshake all together and manually input the users credentials as if you were testing the app at home.  don't let let autoapps sense accounts or check contacts on the users phone. only give it one set as if it was on a new phone with nothing on it but the account you signed on with to test.  And i know there is some type of security that google wants  that i don't know about that you are probably having to use in order to use thier lisence checking system.  Just pretend to put the account in manually every time instead of doing a search so billy bob doesnt use google hes too dumb. red neck paranoid . i don't know its against his religon. he has an account but he doesnt use it so he's not logged in. but he starts using tasker and runs into a wall trying to use all 5 letters of his girlfriends name in autovoice and wham he discovers autoapps.  what happens when he doesn't appear to have a google account.  billy bob is aske to log in ? Am i correct ?  It's something like that and at this point billy bob is not gonna put all 5 of his google accounts on here right now hes only gonna put the one to pass the requirement. So he proceeds to type the credentials in.  Are you saying  that google is gonna remove your app from the play store if they catch billy bob saving his passwords in a text file and copying them in to auto apps or because he has the accessability wench typing them for his mother because she has less teeth than he does.   And are you telling me that every time one of billy bobs friends stores all his passwords in the clipboard they are gonna remove your app from the store.  I think not and you being the app designer can do all this under  the hood and  a million different ways and make it not visible or known at all.   I know that they don't like it when you have a control tower running fully automated and it  starts autofilling out for 1000 email accounts or it is auto typing 10000 logins to 10000 machines and even more sites.  Thats why they are a little wary of auto logins but thats not what we are doing here.  What im calling automatic and storing credentials is a stretch its more like programming the app to manually do what it is already doing automatically.  Automatic manual auto login.  its like saying you have a remote when really you just keep having someone else change the channel everytime someone walks through.  Now i don't want to hear i cant anymore from you sir .  I believe you are the smartest person ive ever heard say that to me.  Now when i was doing this to run a third party google voice app with multiple accounts and way more features than they offered nearly a year after they said no more 3rd party google voice apps and all the other apps went dead that was pushing it but they never took the app down and i had lots of people asking me how but really thats not what we are doing here.   For real bro ive hinted as much as i gonna way way toooooo long i know you know what im saying and you know you thought about it every time you had to fill out one of the blasted feature requests if you didnt' you should just go ahead and get a different job.  but since you made me paint the whole thing out here in front of god and everybody.  now everybody knows .

Unfortunately it doesn't work like that. I can't provide custom, manual credentials to Google Play. It uses what it uses and I can't change that.

What AutoApps can do is simply ask Google Play something like "User wants to purchase this app" and Google Play handles the rest. There's absolutely no way for me to specify which user to use unfortunately.

Sorry!

The problem is that Google doesn't allow this :( For years I have begged them to add the ability for apps to do that, but it's just not possible. Until they allow it, my hands are tied unfortunately.