1
Solved

Cannot install tasker from google play store

It's really frustrating.
I was running an app that I had already paid 4400 won ($4) to purchase and install from the Google Play Store.
At some point, I kept getting pop-ups telling me to use the version I purchased from the play store, and I kept getting links to install tasker in my web browser! I couldn't use the app.
No, I'm not using a cracked version, and I paid $4 to use it from the play store, so why was I getting this error?
It's really frustrating.
I tried reinstalling, but the app doesn't install and the "install" button becomes active again. This happens repeatedly.
I've captured it on video, please fix this issue.

Follow

6 replies

Votes Newest Oldest

Hi there, thanks for the report! Can you please try this version? https://drive.google.com/file/d/1YGuMAWRfyYlUKMdgb4xyVEUfddWz_zzI/view

DK

Installed, and it said

"License error: Invalid package name!"

DK

What is solution?

Are you please able to show me a screenshot of that error so I can check what the issue might be? Thanks

DK

https://imgur.com/a/ZYIbJrQ

check them

Hmm, that seems to indicate that Google Play Store is not enabled on your device. Is it?

DK

No, it is enabled. and I installed all other apps through google play store.

Only "Tasker" is not the app which can be installed through google play store.

DK

Do you have any solution?

If you don't, refund the google play store license and let me buy tasker license(direct license)

or give me another tasker direct license.

I'm trying, sorry, but I've never seen that error before.

Does this version help? https://drive.google.com/open?id=1YGuMAWRfyYlUKMdgb4xyVEUfddWz_zzI&usp=drive_fs

DK

It does not help.

Same error happens:

"License error: Invalid package name!"

Can you please try clearing app data for GOogle Play Store and Google Play Services and see if that helps?

DK

I tried it already and it does not help me.

Check here: https://www.reddit.com/r/tasker/comments/zhqwc0/tasker_license_error_invalid_package_name/

Does that help you in any way? Check the user's fix for it.

DK

I followed the same process, but still failed to install the Tasker app from the Playstore.

Unsurprisingly, the other apps, except for Tasker, install very well from the Play store.

DK

I'm just going to prove my purchase from the Play Store, so it seems like a good idea to issue a new direct license. I've tried countless workarounds and have not been able to install successfully in any case.

J

I am also in the same situation. Paid GPlay version..

image-1712921418877.pngBut whan starting tasker, I am delivered inmediately to a new purchase. See I finally purchased on May 20th 2016.

WhatsApp Image 2024-04-12 at 13.24.31.jpeg

I am delivered directly to this when starting tasker. And seems is a problem with my license

DK

I don't understand the policy. If I made a purchase directly from the Play Store, it should install fine on all devices using the same Google account.

J

Seems to be related to tasker being installed in more than one device.
I must say I havent installed in more than one. The only issue is I have reinstalled the OS in my phone. And.. this restriction was not when I purchased the apk. Not meaning I want to install in more than one, but this should not be an issue.
WhatsApp Image 2024-04-12 at 13.43.10.jpeg

J

No response from Joao Dias so far.
Going to ask help from GPLAY. May be they are more responsive.

I never respond on weekends, sorry. It's my time off 😅. What happens if you install this version? https://drive.google.com/file/d/1YGuMAWRfyYlUKMdgb4xyVEUfddWz_zzI/view

J

Olá, Joao
Nothing new happens. Just installed and the behavior is the same. License invalid toast from the tasker, and immediatelly opens the play store to invite me to a new purchase.

J

Nailed.


In my case, is an unwanted interaction with lsposed. I disabled Lsposed - reboot - tasker. Let it make its inicialisations and configure it till everithing running as expected --> re enable Lsposed...

Obrigado, Joao

DK

This helps me.

But, it does not grant root permission anymore so I manually gave permission via ADB.

Glad you found the issue! Thanks!

Topic is closed for comments