Apktool generating .tmp files after repacking the apk

[GoogleCodeExporter]

I am using following commands for unpacking & repacking the apk on windows 
machine --

apktool d -f -s chromenew.apk

Then I repack the apk with following command  --

apktool b -f chromenew chrome1.apk

After above command,

APKTOOL2243165264778454151.tmp is getting generated in my machine temp folder -

Is there any way to avoid this or  delete this file automatically 
..(\AppData\Local\Temp)

I tried one thing. I use -r  option while unpacking the apk as below
apktool d -f -s -r  chromenew.apk

But with the above approacch, I cant read the AndroidManifest.xml file

Original issue reported on code.google.com by ashiqsay...@gmail.com on 5 Dec 2012 at 10:51

[GoogleCodeExporter]

I did just noticed that /tmp had tons of APKTOOL tmp files. I thought I deleted 
those after build. Will double check.

Original comment by connor.tumbleson on 11 Dec 2012 at 2:45

• Changed state: Accepted

[GoogleCodeExporter]

Fixed.

Original comment by connor.tumbleson on 19 Dec 2012 at 2:12

• Changed state: Fixed
• Added labels: Milestone-v1.5.1

[GoogleCodeExporter]

Thanks man for the fix. How can I get the corresponding jar file 1.5.1

Original comment by ashiqsay...@gmail.com on 19 Dec 2012 at 12:33

[GoogleCodeExporter]

I downloaded the latest version of apktool 1.5.1 & ran it on one apk on 
windows. But still it generates the .tmp files.

Original comment by ashiqsay...@gmail.com on 31 Dec 2012 at 11:00

[GoogleCodeExporter]

I'm having the same problem. I'm using the latest version.

Original comment by ita...@gmail.com on 22 Jun 2014 at 12:03