Error on AndroidManifest.xml..

by ritter.han » Thu, 05 Feb 2009 00:24:29 GMT


Sponsored Links
 Hi, all.

  I'm trying to build the full Cupcake source code,
  And succeeded on my local Linux box.
  But once I copy the same source code to the remote server (Linux
based server)
  it returns the error like as below.

  target R.java/Manifest.java: Development (out/target/common/obj/APPS/
Development_intermediates/src/R.stamp)
  development/apps/Development/AndroidManifest.xml: 74: ERROR Error:
String types not allowed (at 'configChanges' with value 'keyboard|
keyboardHidden|navigation|orientation').
  make: *** [out/target/common/obj/APPS/Development_intermediates/src/
R.stamp] Error 1

  I tried ro delete out folder and 'make clean' also, but failed.

  Please tell me why the same source code return the error like the
above only in the remote server.
  Again, the smae one had been built on my local Linux box (Ubuntu).

  Thanks in advance.
  Shwan.


--~--~---------~--~----~------------~-------~--~----~



Error on AndroidManifest.xml..

by Chronos » Wed, 11 Feb 2009 23:54:28 GMT


 I have the same problem on my current project: Code that is perfectly
valid reports the above error. I first thought it to be some kind of
eclipse integration bug - but if you state, you have this problem on a
remote machine (which you probably do not run eclipse on), I am pretty
sure this is a bug in the SDK.

My temporary solution is: just insert some blank lines, a comment or
something equivalent. The code won't report bugs thereafter (if you're
lucky). Sometimes it even helps to do a clean build. But I find the
frequency of the error rising with the amount of XML in my project.

This is really annoying and frustrating :(. Especially if you're
designing in XML - today I spent about 25% of my time with this bug...
--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Error on AndroidManifest.xml..

by PeteT » Sat, 14 Mar 2009 02:09:53 GMT


 We see this exact same error on a number of systems as well, but
interestingly not on all systems.  Interestingly, we've found that if
we tweak the command line that is generating the error, we can
eliminate the error on all systems.  E.g. on machines which exhibit
the problem, if we run:

p...@android5:$ ./out/host/linux-x86/bin/aapt package  -m -z  -J out/
target/common/obj/APPS/Development_intermediates/src -M development/
apps/Development/AndroidManifest.xml -P out/target/common/obj/APPS/
Development_intermediates/public_resources.xml -S development/apps/
Development/res  -I out/target/common/obj/APPS/framework-
res_intermediates/package-export.apk

Then, we get the error below:
development/apps/Development/AndroidManifest.xml:74: ERROR Error:
String types not allowed (at 'configChanges' with value 'keyboard|
keyboardHidden|navigation|orientation').

However, if we tweak the final argument in the above command line by
pre-pending "../OSP/", as follows:

p...@android5:$ ./out/host/linux-x86/bin/aapt package  -m -z  -J out/
target/common/obj/APPS/Development_intermediates/src -M development/
apps/Development/AndroidManifest.xml -P out/target/common/obj/APPS/
Development_intermediates/public_resources.xml -S development/apps/
Development/res  -I ../OSP/out/target/common/obj/APPS/framework-
res_intermediates/package-export.apk

We do not see the error.   Very odd.   Maybe someone at Google has a
idea?

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Simulate the SIM in the emulator how to do that?

Im actually testing it in an actual device so how about if no device
is available?

-- 

2. How many Android phones have touchscreens?

I can more strongly say that today, to be able to ship an Android compatible
phone (and thus have Market), you need to have a touch screen.

If/when at some point in the future devices without touch-screens are
considered to be Android compatible, appropriate work for existing third
party applications will be done, as we have done in the past: either having
some kind of compatibility so that they can still run with a decent
experience (as was done with the new density support), or applying filtering
so that those applications will not be visible to users until specifically
updated to support the new kind of device (as was done for example for
devices with smaller screens).

While making your app work well with a DPAD is nice, I don't recommend
developers go out of their way today to try to make a touch-oriented UI work
without a touch screen.  That time would be better spent on improving the
touch experience.








> > > 

3. Paket Baru WTI: Internet Unlimited XL naik menjadi Rp 250 ribu/bulan

4. How many Android phones have touchscreens?

5. Reading Notifications

6. Android Java

7. getProviders(true) always return empty list