Has anybody come accross this error before when adding files to include to via ADT?
adt -package -target ipa-test -storetype pkcs12 -keystore my.p12 -storepass mypass -provisioning-profile my.mobileprovision my.ipa my-app.xml my.swf icons Default.png "../../../resources/fonts/FutuBd_.ttf"
In this case I am trying to include a file in the archive that is relative to the output directory.
My output directory is:
My font is in:
However I get the error:
File ../../../resources/fonts/FutuBd_.ttf is not relative to directory c:\projects\game\resources\fonts\FutuBd_ttf
But it actually is!
Anybody have any idea?
If you really have started that line with just 'adt', then you must have cd'd into the AIR SDK's bin folder before starting. You then just refer to 'my.ipa', which would then naturally output to the AIR SDK's bin folder, which I doubt is in that path relative location from the font file.
Also, you have the font path in quotes, does that seem right?
Yeah, sorry Colin, that is indeed what happens (CD first to swf folder). That isn't the exact command line either - I cobbled it as an example. The main point is that at works absolutely fine without including external files (generates an IPA etc), but as soon as I do include files (other than icons or Default.png etc), it doesn't work anymore. Some more info:
- If the files are in the same folder as the swf, and included without a path (filename only) it works fine
- If there is a relative path that is incorrect (i.e. there is no such file), the error is different (file does not exist)
- However, if the relative path is correct (there is a file there) the error is as above
- Quotes or no quotes makes no difference (quotes are there for the 'space in file path' problem)
I ran into the same problem last week. One of my colleagues points out that it sounds like a sandbox issue- so it might be intentional, and not a bug in the ADT. I haven't seen that part of the docs, though. If it's in the docs that way it sounds more like a bug to me....