Closed GoogleCodeExporter closed 9 years ago
It does seem after reading that line from the manifest we forget to pass it
back to the XML parser so it disappears :/
but then aapt has the correct commands to re-add it to manifest. Will have to
double check.
Original comment by connor.tumbleson
on 8 Dec 2012 at 8:56
please update if it is fixed
Original comment by ashiqsay...@gmail.com
on 10 Dec 2012 at 1:28
Fixed in v1.5.1
<?xml version="1.0" encoding="utf-8"?>
<manifest android:versionCode="1700" android:versionName="4.2-517167"
coreApp="true" package="com.google.android.inputmethod.latin"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-sdk android:minSdkVersion="14" android:targetSdkVersion="16">
Original comment by connor.tumbleson
on 17 Dec 2012 at 6:55
I downloaded the latest version of apktool 1.5.1 on windows. But still it
removes the uses-sdk tag.
Original comment by ashiqsay...@gmail.com
on 4 Jan 2013 at 10:07
yes, i have the same problem.please fix it.
Original comment by helin.qi...@gmail.com
on 5 Jan 2013 at 1:42
I see this issue with a test app with code build from the latest repository.
A fix will be great since my business logic requires these tag for processing.
Original comment by rohankap...@gmail.com
on 16 Jan 2013 at 3:25
Tested on OSX still present in 1.5.2
Original comment by MonacoDe...@gmail.com
on 5 Sep 2013 at 10:06
Not a bug.
It must be added at aapt level via apktool.yml, it cannot be left in manifest
and recompiled.
If you require it to be there for analysis purposes, you will have to wait for
2.0 with the --analysis-mode option
Original comment by connor.tumbleson
on 5 Sep 2013 at 10:08
Original issue reported on code.google.com by
ashiqsay...@gmail.com
on 5 Dec 2012 at 11:20Attachments: