yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] cyber_pete:
Hi guys, hoping someone can help me out with this issue. Have looked around but can't seem to find the answer. I have been using apktool for months with no issues. Now all of a sudden, when I decompile any apk, the .9 images become corrupt. I have not had this issue previously. I haven't changed anything on my system. I even tried running apktool through cygwin (I use win 7) and had the same issues. Anyone know what I am doing wrong? Any help is appreciated.
[G1 Android Development] Corey@rabbit:
Are you using a previously themed version of apks? That usually does it for me... just my .02$
[G1 Android Development] tommytomatoe:
Got to love the 9.png. Some devs are lazy/lack the know-how to play with 9.png correctly. So when you decode their themed apks you get those errors. To remedy, you have two choices.

1. Start with a complete stock apk and go from there.

2. If you really want to use the themed apk, you need to note which 9.png are giving you errors. Save the terminal/cmd prompt output. Open up the ORIGINAL unmodded apk with 7zip. Take out the 9.png you need. Put those pngs in the apk that is giving you issues. Then decode. Voila. :-) Then after you build the apk, put the bad 9.png back in with 7zip if you want, or better yet correct them first :-)

tapatalk signature here. lovely.
[G1 Android Development] cyber_pete:
Thanks, I will give that a try.

EDIT:

Just tried with a completely stock apk and am having the same issue. Something must be corrupt on my system. Does anyone know if there are temp files somewhere that I can clear out other than the Windows\Temp folder?
[G1 Android Development] Stericson:
I must say, I am impressed. :)

Very nice job here.

Thanks for your work and time that has gone into this project.
[G1 Android Development] Brut.all:
@Stericson

Thanks :-)

BTW mic_888 had really bad timing with this news on a main site. I'm just about to release next version and it will have quite a lot of nice features/fixes ;-)
[G1 Android Development] mic_888:
@brut.all oops! - don't worry, will do a news update :)
[G1 Android Development] bjehsus:
Can anybody look into using this to get com.facebook.katana 1.1.4 to use the sync provider in OpenEclair?
[G1 Android Development] irkan:
great work man, ... just beautiful! btw why you are not including the youtube demo link in your first post :D
[G1 Android Development] Brut.all:
1.0.0 is here! :-) No smali improvements though :-/

http://code.google.com/p/android-apktool/
[G1 Android Development] domenukk:
Any chance to get this on windows any time soon?

don't have enough hdd space left for a linux vm...

or a version to run on my phone would be nice :p

But it's very cool!

apprechiate your work ;)
[G1 Android Development] olearyp:
Perhaps you should actually visit the GCode page. :)
[G1 Android Development] Brut.all:
Or read my last post:

;-)
[G1 Android Development] mic_888:
Works great on Windows!

Thanks v much - only just installed Ubuntu this morning, but I guess I don't need it anymore :D
[G1 Android Development] Brut.all:
Thanks to eli1981 for helping me with simplified installation on OSX! :-)
[G1 Android Development] eli1981:
Linux - Check

Windows - Check

OSX - Check

Seems like we've them all , now :)

great work Brut.all!
[G1 Android Development] myn:
SHWEEEEET

Nice work. All platforms is huge!
[G1 Android Development] AndroidHAX:
this is amazing, thanks so much for this tool
[G1 Android Development] flak0:
Attempted to decompile the android browser from the Desire rom to port it to the Nexus on Cyan. I am trying to atleast get flash lite in the browser on Cyanogen mod. I successfully decomplied however after making my changes i got the error below when attempting to build. any help is welcome. Thanks
[G1 Android Development] Brut.all:
@flak0

Could you upload these files somewhere? I'll look into them.
[G1 Android Development] flak0:
Def maybe you can help me. I am trying to get the Desire browser to run on Cyanogen mod. I believe by modifying the manifest and other files it can be done. The only prerequisite is the desire cam from Modaco that he posted as this adds htc.framework to the mod. If I am wrong can you help. thanks, your program is awesome.

files below:
[G1 Android Development] Brut.all:
I meant original apk files, so I could see, why some of XML attributes were not decoded ;-)

But I guess it is related to HTC framework - there are some references to resources from range 0x02xxxxxx (Android framework is 0x01xxxxxx). It is hard for me to test HTC apps, because I have my old G1 only. I must rely on people reports.
[G1 Android Development] domenukk:
oh sorry... i didnt think 1.0 could be that epic :P

definitly gonna try check out today... i have so much ideas waiting for some source.

muchas gracias señor
[G1 Android Development] thekdub:
I'm attempting to theme Swype 3.25 beta, but I'm having troubles decompiling the apk. I get the following error:

C:\>java -jar c:\windows\apktool.jar d swype.apk test
I: Baksmaling...
I: Loading resource table...
Exception in thread "main" brut.androlib.AndrolibException: Multiple resources:
spec=0x7f090001 bool/set_help_dialog_font, config=-v13
at brut.androlib.res.data.ResConfig.addResource(ResConfig.java:65)
at brut.androlib.res.data.ResConfig.addResource(ResConfig.java:58)
at brut.androlib.res.decoder.ARSCDecoder.readEntry(ARSCDecoder.java:196)

at brut.androlib.res.decoder.ARSCDecoder.readConfig(ARSCDecoder.java:165)
at brut.androlib.res.decoder.ARSCDecoder.readType(ARSCDecoder.java:130)
at brut.androlib.res.decoder.ARSCDecoder.readPackage(ARSCDecoder.java:105)
at brut.androlib.res.decoder.ARSCDecoder.readTable(ARSCDecoder.java:82)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:48)
at brut.androlib.res.AndrolibResources.getResPackagesFromApk(AndrolibResources.java:316)
at brut.androlib.res.AndrolibResources.loadMainPkg(AndrolibResources.java:51)
at brut.androlib.res.AndrolibResources.getResTable(AndrolibResources.java:44)
at brut.androlib.Androlib.getResTable(Androlib.java:44)
at brut.androlib.ApkDecoder.getResTable(ApkDecoder.java:148)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:98)
at brut.apktool.Main.cmdDecode(Main.java:120)
at brut.apktool.Main.main(Main.java:57)

I've tried the following versions of apktool: 1.3.1, 1.3.2, 1.4.1, and 1.4.2 beta. Anybody have ideas? Thanks.
[G1 Android Development] rahul.oberoy:
I download d apktool n set d adb n java path...... But when im going to select option to decompile apk. ...it ask me to set project path... Option 22

Plz tell me how to set project path in apktool
[G1 Android Development] tommytomatoe:
You must be thinking of apkmanager. Apktool is the tool that apkmanager uses.

But besides that sorry I cant help much further, other than to say to use apktool manually.

tapatalk signature here. lovely.
[G1 Android Development] coolshadow:
Hello, everyone, I have problems with apktool's smalidebugging feature.

I use apktools like below

1. apktool d -d xxx.apk dir

2. apktool b -d dir

If I did like above, the first step is Ok, but for the sencond step, I'll get errors like below:

I: Checking whether sources has changed...
I: Smaling...
Exception in thread "main" java.lang.NullPointerException
at org.jf.util.PathUtil.getRelativeFile(PathUtil.java:44)
at org.jf.smali.smaliFlexLexer.getSourceName(smaliFlexLexer.java:2569)
at org.antlr.runtime.CommonTokenStream.getSourceName(CommonTokenStream.j
ava:345)
at org.antlr.runtime.Parser.getSourceName(Parser.java:88)
at org.jf.smali.smaliParser.getErrorHeader(smaliParser.java:324)
at org.antlr.runtime.BaseRecognizer.displayRecognitionError(BaseRecogniz
er.java:192)
at org.antlr.runtime.BaseRecognizer.reportError(BaseRecognizer.java:186)

at org.jf.smali.smaliParser.method(smaliParser.java:1620)
at org.jf.smali.smaliParser.smali_file(smaliParser.java:561)
at brut.androlib.mod.SmaliMod.assembleSmaliFile(SmaliMod.java:71)
at brut.androlib.src.DexFileBuilder.addSmaliFile(DexFileBuilder.java:43)

at brut.androlib.src.SmaliBuilder.buildFile(SmaliBuilder.java:101)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:48)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:35)
at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:222)
at brut.androlib.Androlib.buildSources(Androlib.java:179)
at brut.androlib.Androlib.build(Androlib.java:170)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:174)
at brut.apktool.Main.main(Main.java:59)

The strange thing is that, If I use apktools like below, everything is Ok,

1. apktool d xxx.apk dir

2. apktool b dir

I also tried

apktool d -d xxx.apk dir

apktool b dir

and

apktool d xxx.apk dir

apktool b -d dir

Both compiles well.

So I don't know why cause this. As I need to use the smalidebugging feature, so I should use -d switch. But the problem is when I use the switch, apktool faild when rebuild the apk file.

Anyone can help me?

Thanks:)
[G1 Android Development] blackdog7:
Hi Brut.all!

I used through many years windows mobile. Because the translations was to my language (Hungarian) very-very wrong and rarely too long, I modified the *.mui files with Reshaker.

Now I'm using Sensation I'm using Sensation with android and I want to edit the Hungarian language files.

Example by the new Sensation 3.5 are the translated rosie buttons (All apps, Phone, Settings) too long and the text of "All apps" has not enough space. This is in Hungarian: "Minden alkalmazás".

I copied from rosie.apk the resources file, but how can I edit and copy back to the a new rosie.apk. Can you tell me the whole method? Or am I asking too much? :(

Thx and sorry for my English, I hope you understand my wish.

Blackdog
[G1 Android Development] dsb9938:
Error Decompiling SystemUI.apk from Sense 3.5 ROM

Been using this a lot, def not a noob.

Never had an issue that wasn't my fault, until now. At least I think. Please prove me wrong.

My SDK is completely updated, aapt from it moved to apktool folder.

Latest apktool patched for ver 13.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Dennis1\Desktop\Android Dev ****\Apk Tool>apktool if c
om.htc.resources.apk
W: Config flags size > 32. Exceeding bytes: 01000000.
W: Invalid config flags detected: dimen-hdpi-ERR0
W: Config flags size > 32. Exceeding bytes: 02000000.
W: Invalid config flags detected: dimen-hdpi-ERR1
W: Config flags size > 32. Exceeding bytes: 04000000.
W: Invalid config flags detected: dimen-hdpi-ERR2
W: Config flags size > 32. Exceeding bytes: 05000000.
W: Invalid config flags detected: dimen-hdpi-ERR3
W: Config flags size > 32. Exceeding bytes: 01000000.
W: Invalid config flags detected: integer-hdpi-ERR4
W: Config flags size > 32. Exceeding bytes: 02000000.
W: Invalid config flags detected: integer-hdpi-ERR5
W: Config flags size > 32. Exceeding bytes: 04000000.
W: Invalid config flags detected: integer-hdpi-ERR6
W: Config flags size > 32. Exceeding bytes: 05000000.
W: Invalid config flags detected: integer-hdpi-ERR7
I: Framework installed to: C:\Documents and Settings\Dennis1\apktool\framework\2
.apk
C:\Documents and Settings\Dennis1\Desktop\Android Dev ****\Apk Tool>apktool if f
ramework-res.apk
I: Framework installed to: C:\Documents and Settings\Dennis1\apktool\framework\1
.apk
C:\Documents and Settings\Dennis1\Desktop\Android Dev ****\Apk Tool>

Pretty sure the msgs above can safely be ignored. Is that correct?

Then when I do "apktool d SystemUI.apk" I get a bunch of these:

Error occured while disassembling class Lcom.android.systemui.statusbar.preferen
ce.AirplaneMode$2; - skipping class
java.lang.ArrayIndexOutOfBoundsException: 8
at org.jf.dexlib.Debug.DebugInstructionIterator.DecodeInstructions(Debug
InstructionIterator.java:199)
at org.jf.baksmali.Adaptors.MethodDefinition.addDebugInfo(MethodDefiniti
on.java:495)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefini
tion.java:297)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.ja
va:130)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMethods(ClassDefinition
.java:322)
at org.jf.baksmali.Adaptors.ClassDefinition.writeVirtualMethods(ClassDef
inition.java:307)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java
:136)
at brut.androlib.mod.BaksmaliMod.disassembleDexFile(BaksmaliMod.java:188
)
at brut.androlib.src.SmaliDecoder.decode(SmaliDecoder.java:48)
at brut.androlib.src.SmaliDecoder.decode(SmaliDecoder.java:33)
at brut.androlib.Androlib.decodeSourcesSmali(Androlib.java:68)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:85)
at brut.apktool.Main.cmdDecode(Main.java:120)
at brut.apktool.Main.main(Main.java:57)

It decompiles the rest correctly, just not these parts.

Any ideas?

D
[G1 Android Development] thejondude:
^ having the same issue
[G1 Android Development] chrisch1974:
This is a known problem with HTC Sense 2.3.5 roms. Seems that HTC uses a custom aapt. And therefore not all p as free can be recompiled. Only chance is to work with keep-broken-res and merge them manually.
[G1 Android Development] dsb9938:
So basically we're hosed, just like on the m10 stuff?

D
[G1 Android Development] tommytomatoe:
For the time being...yes. but our buddy Brut.all is still around. If he's interested he can do some major good for the modders out there.

tapatalk signature here. lovely.
[G1 Android Development] Pneuma1985:
brut please update for sense 3.5 please... It would be a huge help for all of us...
[G1 Android Development] pendo:
Yeah, I know of some folks who'd just LOVE to see apktool handle decompiling/recompiling of m10.

That m10 stuff makes me all the more content playing around with plain-jane aosp:)
[G1 Android Development] tommytomatoe:
I know the feeling! I'm still playing with sense 1.0 and aosp myself. :-) First Rom will be sense 1.0.

tapatalk signature here. lovely.
[G1 Android Development] Pneuma1985:
No Im not even talking about the m10's it has tons of erros b/c htc uses a different aapt in sense 3.5.
[G1 Android Development] splattx_x:
Hi! first of all, great app!!!

But I'm facing some problems recompiling an apk. I'm trying to remove Touchwiz's dependencies for the native samsung keyboard AxT9IME.apk. I've already deodexed the app and then I can extract the app OK. I can modify files and rebuild without problems but if I want to "add" a new file, which I need in order to remove the dependency from Touchwiz. I get this error

Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, /tmp/APKTOOL5164481783268420841.tmp, -I, /home/francisco/apktool/framework/1.apk, -I, /home/francisco/apktool/framework/2.apk, -S, /home/francisco/dev/Apps/./AXT9/extracted3/res, -M, /home/francisco/dev/Apps/./AXT9/extracted3/AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:193)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:301)
at brut.androlib.Androlib.buildResources(Androlib.java:248)
at brut.androlib.Androlib.build(Androlib.java:171)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:174)
at brut.apktool.Main.main(Main.java:59)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, /tmp/APKTOOL5164481783268420841.tmp, -I, /home/francisco/apktool/framework/1.apk, -I, /home/francisco/apktool/framework/2.apk, -S, /home/francisco/dev/Apps/./AXT9/extracted3/res, -M, /home/francisco/dev/Apps/./AXT9/extracted3/AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:191)
... 6 more

aapt is in my path and I'm using android-sdk "10". I tried googling it but I didn't find anything similar to my particular situation.

Any help would be appreciated! Thanks!!
[G1 Android Development] roofrider:
C:\Users\Raja>apktool b SystemUI SystemUI.apk
Exception in thread "main" brut.androlib.AndrolibException: brut.directory.PathN
otExist: apktool.yml
at brut.androlib.Androlib.readMetaFile(Androlib.java:142)
at brut.androlib.Androlib.build(Androlib.java:159)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:174)
at brut.apktool.Main.main(Main.java:59)
Caused by: brut.directory.PathNotExist: apktool.yml
at brut.directory.AbstractDirectory.getFileInput(AbstractDirectory.java:
103)
at brut.androlib.Androlib.readMetaFile(Androlib.java:138)
... 4 more

C:\Users\Raja>

this is wat i got wen i tried to build.....any help wud be really appreciated:)

edit: fixed. my mistake.
[G1 Android Development] pendo:
If they are using a customized aapt, then there's probably nothing brut.all can do. Apktool is based entirely off of aosp resources. Reverse engineering closed source is no simple task.
[G1 Android Development] sendan:
Great tool, it worked flawlessly for all my apks except one!

It seems I'm having trouble with building the SystemUI.apk, framework-res.apk and twframework-res are both installed.

Here's the error: (I'm not making any changes to the package)

C:\theming>apktool b SystemUI
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
C:\theming\SystemUI\res\layout\status_bar_expanded.xml:12: error: Error: No reso
urce found that matches the given name (at 'layout' with value '@touchwiz:layout
/quick_panel_call').
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutExce
ption: could not exec command: [aapt, p, -F, C:\Users\Jon\AppData\Local\Temp\APK
TOOL8249204731835465733.tmp, -I, C:\Users\Jon\apktool\framework\1.apk, -S, C:\th
eming\SystemUI\res, -M, C:\theming\SystemUI\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:193)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:301)
at brut.androlib.Androlib.buildResources(Androlib.java:248)
at brut.androlib.Androlib.build(Androlib.java:171)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:174)
at brut.apktool.Main.main(Main.java:59)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\U
sers\Jon\AppData\Local\Temp\APKTOOL8249204731835465733.tmp, -I, C:\Users\Jon\apk
tool\framework\1.apk, -S, C:\theming\SystemUI\res, -M, C:\theming\SystemUI\Andro
idManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:191)
... 6 more

C:\theming>

EDIT: I tried to compile on a different windows 64 bit PC and I got the same exact error, I'm assuming I"m screwing something up so any help is appreciated!
[G1 Android Development] pendo:
Did you install Samsung framework files to apktool? If not, then run this:

apktool if twframework-res.apk twiz

The verbose output should say Framework installed to apktool/framework/1-twiz.apk. You can substitute something else if you prefer, I just made up "twiz" right now. It's just a tag so that you can call it in the next step:

apktool d -t twiz SystemUI.apk
[G1 Android Development] sendan:
Yep it was installed, but just to make sure I did it again with a tag. The output says it's installed to apktool/framework/2-twiz.apk.

However, that didn't seem to make any difference, according to the log it only uses 1.apk. (which is the framework-res.apk)

EDIT: For the record, I was able to recompile SystemUI.apk with apk manager v4.9 (and I'm assuming apk manager 4.9 used an older version of apktool), however it always caused force closes if i tried to compile the apk with the status_bar_expanded.xml.
[G1 Android Development] Eirki:
Great tool! I've been using it a lot for the past months.

Is there any chance for a fix regarding the problem with compiling xmls with capital letters?

There seems to have been some development in the last few days, where someone figured out how to do it in linux:

Here's the link to the post.

I don't know much about programming, but I've seen the resulting theme manager theme, and it does include xmls with capital letters. If I try to compile and decompile it using apk manager, I get the same old error.

Any chance at all of being able to it in windows?
[G1 Android Development] pendo:
Have you tried decompiling twframework-res.apk? The error is listing layout

/quick_panel_call...do you see it?
[G1 Android Development] sendan:
Yes that file is in the twframework-res.apk
[G1 Android Development] pendo:
It sounds like you're doing everything right. It's just not also checking 2-twiz.zpk.

Well, let's try to force it to use it. Edit the apktool.yml file to read like this:

version: 1.4.2.269870b
apkFileName: SystemUI.apk
isFrameworkApk: false
usesFramework:
ids:
- 1
- 2
tag: twiz

See what happens then.
[G1 Android Development] sendan:
Wow...apparently you just fixed a problem I've been bashing my head on my keyboard to for 3 days in about 3 hours, thanks!!

EDIT:Well although I can get the apk to build it doesn't work when I push it, do I have to change something so it uses 2.apk while decompiling as well?
[G1 Android Development] tommytomatoe:
Are you placing the original meta-inf into the new apk prior to pushing? This step is crucial and often forgotten.
[G1 Android Development] sendan:
Yeah I did forgot that, but I'm still having the same issue. (statusbar just not showing)

Also...you guys are ridiculously helpful, thank you!
[G1 Android Development] tommytomatoe:
No problem. Pendo is a gangster beyond belief :-)

As for status bar....

SystemUI doesn't like to be pushed all the time. Often I get that issue too and have to flash. I try to avoid flashing when I can help it. But sometimes you have to do it. Also, you can check and make sure you have the correct permissions on the apk. Those are your two most common errors when pushing files "live".

Also, try this:

adb shell stop

adb push $file $destination

adb shell stop
[G1 Android Development] sendan:
Okay I double checked my permissions and all were set properly. I also made a .zip and flashed it/wiped dalvik just to be sure and there is no change.
[G1 Android Development] splattx_x:
Do you think that the quoted solution could work with my quoted error message? I'm dealing with a Touchwiz .apk too. I can't make sense of the error message... and only happens if I add a file to the apk and try to recompile. I think when recompiling it's not using twframework properly...
[G1 Android Development] sendan:
No, according to your log it is properly using both 1.apk and 2.apk.
[G1 Android Development] pendo:
Lol.

Well I'm not sure. Theoretically, it should've needed the extra resources in order to decompile. The apktool.yml file is only used for recompile. So I guess go ahead and decompile with the tag. Then edit the apktool.yml file if need be, and try again.

Additionally, you should definitely be pushing SystemUI while core is stopped. That can either be done in recovery or I like to just do adb shell stop. (I should've charged Tommy more when I told him that trick http://dl.dropbox.com/u/10532974/emoticons/stir_the_pot.gif) And like he said, make sure to reuse BOTH the AndroidManifest and META-INF folders from the original.

If that doesn't work, another option would be to build your own resources.arsc that goes inside brut/androlib/android-framework.jar from apktool.jar. That's a pretty hacky job, especially since I have no idea if it would work lol. In theory it should though.
[G1 Android Development] sendan:
On a random hunch I also replaced the AndroidManifest.xml with the one from the original SystemUI.apk and it works now!

However I'm wondering if there's a reason you didn't tell me to replace this, will it cause problems if I start editing images and xml or anything down the road?

EDIT: Oh look at that...guess we both posted at the same time...okay well you guys fixed my problem then. Thanks!! :D :D :D

I'm overwhelmed with happiness that I can finally finish my theme properly now...weeoooooo!
[G1 Android Development] pendo:
Yeah, if you're going to reuse the signatures, then you need to do the same with the manifest. I actually do this as standard practice on all apks, unless I'm actually changing something in the manifest itself.
[G1 Android Development] splattx_x:
Ok, that's good then. Any ideas as to why it can give this output? The error message is not very explicit...