I have two projects of Android.
p1. Notepad project(Big project)
p2. Sync-Android( its an appengine connected Android project)
(p2 is a sample project provided by Google Plugin and hence very small in size.)
I wanted to merge both of them, I read some posts here on StackExchange. And copied all the source files from p1 NOtepad sample project to Sync-Android and I also merged res folder of both.( I will take care of main.xml and string.xml, p2 is a small project so not a problem.)
But I get the problem of R class of android. This may be because the xml files were not built and didnt insert values in gen>R.java. That is the code that i copied have error like.
R.string.button_dont_save
its showing error. Is there any way dealing with that...
PS:-I have read merge two android projects and the easy solution is making library of one project. I cannot make a library for a specific reason and so I have to merge both the projects.
Summarry:- If I can resolve the error of Resource class i.e
R.string.button_dont_save, R.style.Theme_Notepad etc.
I think i will be able to handle it.
Thanks
I think that resource or the string is missing in resources/strings.xml. Check the existence of the resources and strings. If you are merging two projects, then you should not replace the resources. you should append the ones resources to other to the same file name. If you properly do this, then it should work. try cleaning the project and re-building it.
Related
I need to pack my project into a jar for others to use. But when I run the program, it throws a lot of Nullpoint exception, the program can not find the correct R.id.
One solution is to use the getIdentifier() replace R.id.
the other is to use a public.xml.
and use android stuido export a .aar file.
But I have too many R.id in the project, it's a lot of work to use first and second way. And project is developed by Eclipse, can not use aar file.Is there a other simple way.
I have a Library project set up and a project which depends on this library project - Everything compiles fine and I've had the Dependent project running fine however;
I'm have an intermittent problem however while using an Activity from the Library project.
My Library project can be "unchecked" as a library project and the "picker" Activity can be run in isolation. Running the Library project in it's own right works fine with no problems.
When I use the Library project (and the "picker" Activity) from the dependent project it gives me either NullPointerExceptions (or historically DexOp) errors saying that the "picker" Activity can't find it's resources.
Can anybody tell me if they have experienced this before?
EDIT
Manually copying the layout.xml used by the Library project activity to the dependent project makes the project open the "picker" Activity correctly. Is this required?! Surely not? This further makes me wonder if there is a problem with merging/referencing the integer id's from R.java in the Library project.
EDIT
I'm not sure if this is of any consequence, but one of my Library projects is a wrapper around a set of custom views used in different front end projects.
These custom views each have an Activity so that they can be tested in isolation.
One of these view's has custom attributes, which while running in isolation work very well. However, it doesn't seem like the dependent project correctly pull's in the attributes and keep's them in their original namespace, causing the imported layout's to throw compilation errors:
[2012-05-16 12:07:28 - Project] D:\opt\workspace\CustomGlowList\res\layout\main.xml:14: error: No resource identifier found for attribute 'listId' in package 'com.company.library.glowlist'
[2012-05-16 12:07:28 - Project] D:\opt\workspace\CustomGlowList\res\layout\main.xml:14: error: No resource identifier found for attribute 'type' in package 'com.company.library.glowlist
EDIT
DexOp errors were solved by removing a duplicate file name which was present in the Dependent project. Not sure if the file name was the problem or the contents of the file.
EDIT
I've been unable to find a solution to this problem as of yet (although #yorkw's answer certainly helps with the xml attributes! Thanks).
I have managed to make this problem intermittent however:
I have gone through each of the library projects and ensured they all had their own namespace (ie, com.company.library.component1, com.company.library.component2 etc). After a couple of clean's (each project ordered with the correct precedence) this problem resolves itself, however does eventually come back when switching around library/not a library to test components.
Cause:
Issue 9656: Library projects don't support custom XML attributes for custom classes
Solution:
Upgrade to latest SDK & ADT version (fixed was released since r17) and use http://schemas.android.com/apk/res-auto as custom attributes' namespace URI, see Revisions for ADT 17.0.0:
Added support for custom views with custom attributes in libraries. Layouts using custom attributes must use the namespace URI http://schemas.android.com/apk/res-auto instead of the URI that includes the app package name. This URI is replaced with the app specific one at build time.
Related Topic:
Help with a custom View attributes inside a Android Library Project
not sure how you use the android library , but i've done this thing a lot of times without any problems , so please have a reading of the next things regarding using android libraries:
in order for an android project to use an android library project , you can either edit the "project.properties" and add the path to the library project there , or , much easier, right click the project (that uses the library project) , choose "android" category , and choose there "add" and choose the library project.
in order to make the android project to always open the android library project , also choose "java build path"->"projects" and choose the library project.
on the "project.properties" , try to set the target to the same target for both projects , and to the newest one that you have (latest now is 15) ,even if you can't test the app on this android version .
source files and all resources files (in the res folder) are ok to be used on the library projects.
assets folders cannot be used inside the library project . only on the android project that actually runs , the assets folder can be used . same thing goes to the proguard file .
the manifest of the library projects almost doesn't need to have almost anything . see this post for more information: https://stackoverflow.com/a/10445630/878126 . if there are activities on the library project that you wish to be able to access via the project that use it , don't forget to include them in the manifest of the android project (no need to write them in the manifest of the android library) .
remember to run lint before you export the app . it gives you plenty of warnings , but the most important warning is when you use too-new functions that cannot run on the range of APIs that you target . this is important for libraries since it's easy to get lost if there are multiple sources .
if you wish to extend activities on the android library , you need some kind of a method to go between them . the only way i know of is to extend the application and let it be the manager of how to create an intent for each of the activities . i think you can do other tricks , but they are all probably similar to this one.
if you have the same resource (any resource on the "res" folder) on both the android library and the android project, the one on the android project will replace the other one . this has advantages and disadvantages . remember that you can't have different file extensions for the same resource .
The problem was being caused by the R files from each of the Library projects not correctly being built and referenced. The resource files are built and referenced directly from the calling project.
Each of the Libraries need to have unique package as defined in the AndroidManifest.xml. This leads to each of it's resources being compiled in that unique namespace within the calling project alongside the Library jar which contains the class files.
The problem becomes intermittent when switching between a library and a runnable project because a clean and build needs to take place to regenerate these files as it isn't done automagically when unclicking the Use as library checkbox, where as the jar (and java classes) don't require as much coaxing for them to be correctly referenced as the library projects references them when acting as a Library.
This can lead to intermittent and also varying errors including missing references, DexOp and NullPointerExceptions depending on to what degree the R.java files have been mangled or partially built and what conflicts are taking places between packages.
I have same issue like, I have one library project and it has some activity.
When I was calling library project's Activity from my Main project, layout files resources were not getting loaded properly for the libray project's activity and giving "nullpointer exception" or "class could not be loaded", etc.
Solution: I have noticed that same layout file name is getting used in my Library project and Main project. I have just renamed those activity and it is solved.
May be this will help you.
I had similar issue when referencing Library project inside the Android App project. I deleted the R.java file from Library project so it generated again and App picked up the generated file. You should see the generated R.java file under your app project->gen->library_namespace_R.java.
I am trying to create a android project with two libraries,however, I have been able to link the two libraries I created with my android project.
I have same xml name in two libbaries,when I am compiling my project, the R.java file is getting compiled in my new project and I am getting only one xml file from the two libraries. how could I link the two libraries in my android project with the same xml names? I know it can be done with diff names but I want the same name.
Are you saying you have say strings.xml in /res/values in both library projects and expect to get more than one strings.xml in your consuming project?
From what I experience, if I have strings.xml in library projects and also in my consuming project, the resulting R.java will have the values from all 3 merged together, with any duplicate entries having the value as defined in the consuming project.
Not possible. That's the way library projects are designed to work. Resources are merged into the parent project. If you want values from both libraries to make it in, they need to have different resource IDs, and even then you'll have one resource file (unless you have different file names to start with).
The only way you could get this to "work" is to do something with your build process renaming the files, which is doable, but not trivial, especially if there are possible resource ID conflicts and even harder if your main project needs to use any of those resources directly.
I am currently working on a Android Project where we are expected to merge our App with 2 more apps from vendors who wouldn't be sharing their code.So just wanted to know Is there any way we could just include there Source code as JAR Files in our project and then include their resources and point to them(I did do it using getResources().getIdentifier("splash", "layout", getPackageName()) But Its still not working ?? I think I have tried all possible methods so hoping you guys could help me with this.
To quote CommonsWare from this question:
Bear in mind that your packaged classes cannot reference resources (at
least not via R. syntax), and that JARs cannot package resources,
manifest entries, etc. If all you are trying to JAR up is pure Java
code (perhaps using Android APIs), then you should be fine.
Basically, you can only use JARs that contain pure java as libraries in your app, not entire other projects.
The Activities can be compiled into a jar and added to the main Android project and we need to add their project's resources into your Project. The only we could make it work is using the getResources().getIdentifier("splash", "layout", getPackageName()). Even the Widgets like TextView, Button and all those should be referred to using the getResources() method. Like, for example, If you want to perform a action on particular button then we need to identify them by getResources().getIdentifier("Button" /*id in the XML File*/, "id"/*type*/, getPackageName()).
One more thing: you need to specify all the Activities in your Main Android Project's AndroidManifest.xml file with their package name. I hope this solves something.
In order to support faster build times, the r16 tools are creating their own jar files inside of Android Library Projects. You can use this feature to solve this issue. If a vendor would like to release their Android Library Project but without source code, they can make a copy of that Android Library Project that contains everything except for the source code tree. Next, include the jar file from the original Android Library Porject (the one that the r16 tools built.) This will allow you to have a component you can distribute that does not require source code. The consumer of this new Android Library Project will need to manually add any necessary meta data to their own project's AndroidManifest.xml file as needed (Activities, Providers, Permissions, etc).
I have one Project let us say pattern project. There are all sources and layouts for the different versions of the other projects. Without the drawables, because the other projects have different.
There are also 2 projects which use this pattern project es library. Which has there own drawable ressources and some own layout xml files.
This is working for me, I can compile it and on the device it is running.
But every time the workspace is building I get a lot of errors from the pattern project that there are no ressoruce files which are uses in the layout xml files.
res\layout\news_list.xml:9: error: Error: No resource found that matches the given name (at 'src' with value '#drawable/logosmall').
Is this normal? I'm using the wrong way to do it? How can I fix this?
I hope anyone of you can help me.
A Library project is treated as a normal Android project by the build process, so if you want it to build without errors you have to include all referenced resources (or at least similarly named placeholders) in the Library project itself even if they are to be "overridden" by your application projects.