aapt

I have files in res/raw that I would like to open like this: AssetFileDescriptor afd = getResources().openRawResourcesFd(); This allows for, e.g., getting the definitive file size via afd.getLength() , which InputStream.available() does not promise, even if it seems to generally work. However, when I try this it fails: java.io.FileNotFoundException: This file can not be opened as a file descriptor; it is probably compressed These are just small text files. What's the problem? aapt compress most resources as part of the build process. According to this article which quotes the aapt source, the

I have two android apps using a common library. Each project defines its own background images for the splash screen and a few others. These images have the same names in both apps. When I build/run from eclipse, each app uses the correct background images. However, when I run my ant build file, the contents are mixed up when packaging resources and the same images are used for both applications. I am sure there is a cache somewhere that I need to clear but I can't find it (running on MacOSX Lion). I tried the -f option of appt , but still the same problem. Anybody knows how to fix this? run

How to check if apk is debug or release signed? Is there any direct adb command to verify apk signature? Tried the following dumpsys and aapt commands, but I am not able to find the exact flag adb shell dumpsys package <package name> aapt dump badging <apk file> How to find out the given apk is debug or release signed? How to know which builds (user, userdebug or eng) we can install this apk? Rohith Krishnan If you want to check whether the apk is debuggable use the below aapt command. aapt dump badging /path/to/apk | grep -c application-debuggable Outputs 1: Debuggable Outputs 0: Not

I'm using Eclipse 4.2.2 with Android SDK 22.0.1 to construct an Android application which uses the Facebook and Google Play Services lib. However I'm stuck with a problem: every time I include one or both of the library the aapt verbose mode crash in some point like this (I assume this also crash with verbose mode off, because the R.java files are not created on my project): [2013-06-21 01:33:40 - Project] (new resource id com_facebook_placepickerfragment_list_row from /Users/Solens/workspace/FacebookSDK/res/layout/com_facebook_placepickerfragment_list_row.xml) [2013-06-21 01:33:41 - Project]

I have downloaded latest revision (r14) yesterday. but getting this error while running any application ERROR: Unknown option '--no-crunch' Please help... I have recently faced this issue. But it is now solved . After updating to ADT r14, go to Window -> SDK Manager (in Eclipse) Check on 'repository', uncheck "installed" Wait for packages to load, then select all support packages, accept all and install them Restart Eclipse Now you can run your apps on new ADT r14, without 'crunch' errors. I think the --no-crunch was dropped from platform-toosl revision 7. aapt (part of platform-tools)

问题： MAC终端使用aapt指令"aapt dump badging xxx/xxx/xxx.apk"查看apk包名和activity时报错提示"command not found"，如下图： 解决： 该问题由于未配置aapt环境变量导致，在.bash_profile中配置AAPT_HOME和PATH即可解决。 前提：已安装配置Android SDK （1）打开配置文件(终端打开) 打开指令：open .bash_profile （2）配置环境变量 环境变量如下： export AAPT_HOME=/Users/xmly/Desktop/auto/UItest/app_autotest/android-sdk-macosx/build-tools/29.0.2 export PATH=$PATH:$AAPT_HOME 备注： AAPT_HOME后为build-tools下一级文件的路径（拖动文件至终端可获得文件路径） path后变量由“：”隔开，直接在原path后新增“:$AAPT_HOME”即可 （3）使配置文件生效 生效指令：source .bash_profile （4）验证配置成功 验证指令：aapt（若出现aapt说明信息则配置成功） 来源： https://www.cnblogs.com/mini-monkey/p/11694340.html