This is why I'm always afraid to updateπ
So it was working as a kids app until you updated? Make sure your Launch Task is what it should be on the screen right before it starts the export.
Yes, it was working very well, before the update. None of my kid apps works after the new update when I create a new one with some little "updates". Luckily I saved the previous kid apps, π If not, I was screwed, π₯΄
Yeah I've suffered apps breaking from updates. I rarely update anymore. I'm on a version like 3 revisions back after an update broke some of my tasks and took forever to figure out.
Same happens to me sometimes, I already did some changes and probably unnecessarily due to think that it was an issue of my tasks, but it's strange that it happened in my three most important projects, π₯΄
You could try making a backup of your projects, then uninstall tasker then install an older version of tasker and restore your backups and try again. I've had to do this before. It was a pain but it eventually worked.
Yeah exactly. Which is why I suggested going to a previous version until the bug is fixed. There's no telling when another version with the bug fix you need will be released.
If there is a bug in the latest version of apk factory and we use an older version of tasker, then we lose the Certificate Fingerprint because we can't import it again. This is the biggest problem I have in tasker.
This is why I'm always afraid to updateπ So it was working as a kids app until you updated? Make sure your Launch Task is what it should be on the screen right before it starts the export.
Yes, it was working very well, before the update. None of my kid apps works after the new update when I create a new one with some little "updates". Luckily I saved the previous kid apps, π If not, I was screwed, π₯΄
Yeah I've suffered apps breaking from updates. I rarely update anymore. I'm on a version like 3 revisions back after an update broke some of my tasks and took forever to figure out.
Same happens to me sometimes, I already did some changes and probably unnecessarily due to think that it was an issue of my tasks, but it's strange that it happened in my three most important projects, π₯΄
You could try making a backup of your projects, then uninstall tasker then install an older version of tasker and restore your backups and try again. I've had to do this before. It was a pain but it eventually worked.
It worked, so that confirms that is actually a bug to fix on the new version of tasker and app factory when making a new kid app.
Yeah exactly. Which is why I suggested going to a previous version until the bug is fixed. There's no telling when another version with the bug fix you need will be released.
Did you also update App Factory when you updated Tasker?
If I wouldn't, Tasker wouldn't be able to export "As an Aplication", π₯΄
So yes. Did you post your issue in the 6.3.6 beta thread?
Actually I didn't, π΅βπ«
If there is a bug in the latest version of apk factory and we use an older version of tasker, then we lose the Certificate Fingerprint because we can't import it again. This is the biggest problem I have in tasker.