I've been working on this project for months, and when I started out I knew nothing about android dev, gradle or signatures. Since Android studio was also quite new when I started in June, and updates often brought errors in the gradle, the code is a bit messy.
Now, I've been trying to get the new support library imported into my project - without success. Re-importing the project seems to fix this nice and easy, but this means I have to replace the old project(package anomaly). My question is, since this app is already deployed, will I loose the old signature and with it the possibility to update the app on Google Play store?
Hope to hear from ye! Thanks.
[EDIT]
Yep, worked like a charm :) Thank you Samuel!
If I am answering the question I think you are asking, can you change the package name and still upload the application as "updates" to one that is already in the market the answer is no.
Once an application is uploaded to the market, pretty much everything can change except the key and the package.
As long as you still use the same signature and key then you should be able to compile with different things and still upgrade successfully. I highly suggest compiling what you have now and trying to upgrade it in the app market and that will very quickly determine whether or not it is possible. If you do this post back on this post if it worked or not for everyone else to see
Related
I've been developing using the Android L preview. Today I've spent all day trying to set up eclipse so that I can develop using the new APIs. I've run into so many problems, and have hashed most out by just making a new workspace.
A persisting problem is the one shown below. These resources are in the R.java file and are in the resource folder. I haven't moved anything or changed anything about the project other that the target build sdk. The error is occurring any time I try to access a resource using the format R.XXX.XXXX. What could the reason be? Any ideas?
EDIT: NEW ANSWER
Something was just bugging out. Not sure what, but after re-downloading the bundle, downloading API 21, restarting laptop etc etc my same project is running just fine. Hopefully this isn't temporary.
Bundle: https://developer.android.com/sdk/index.html?hl=i
PREVIOUS ANSWER: Some of my resources had digits in the filename.
This doesn't seem to be documented. I found this by first trying to start from scratch, building up my app in a new project. This worked until I had to make a big jump, adding lots of activities at the same time due to dependencies, and this caused the same error to occur. I then starting bit by bit stripping down my app. Found that upon deleting those resources, the errors subsided.
I thought that a-z and 0-9 were allowed. Files with these characters worked just fine in previous Android versions, but it seems that updates made when switching to Android 5.0 makes 0-9 invalid.
Can anyone else confirm this?
I am new to Android Development/Java Programming/Eclipse so please bear with me. I've been going through the Android Developer Training (developer.android.com/training) and the Hello Android book by Ed Burnette and keep running into a problem that is making it difficult to move forward. I'll do my best to describe it and am hoping that the community can help me resolve it.
I began seeing this issue with the Android Developer Training (around Adding the Action Bar -> Adding Action Buttons) and it became impossible to circumvent at Hello Android's 3.3 Creating Opening Screen when I tried adding the Sudoku buttons. The only change I made when going through Hello Android was adding the Android Development Toolkit (ADT) for Eclipse. I don't recall this being a required download going through the Android Developer Training page so I am wondering if its addition could have contributed to the problem.
The issue that I keep running into is that when I go to build the project, Eclipse keeps telling me:
action_settings cannot be resolved or is not a field
activity_sudoku cannot be resolved or is not a field
container cannot be resolved or is not a field
fragment_sudoku cannot be resolved or is not a field
sudoku cannot be resolved or is not a field
I've tried several fixes that I saw on in the forum including deleting the import.android.R from the sudoku.java file in my src folder but that brings up a bunch of errors that say R cannot be resolved into a variable. I've tried cleaning and rebuilding and restarting Eclipse, methods that occasionally worked before Hello Android and the plugin, but keep getting the same errors. I've also tried setting to Android 3.0 and higher thinking that might be an issue but there was no change. Occasionally I get another error regarding not being able to find the path for a container but I've been playing around with the IDE for 15 minutes and can't seem to get it to pop up again.
I could really use some help on this.
Hope to hear from you,
Yusif Nurizade
This solution may, first and foremost, demonastrate how green I am with Android programming but I believe I found the solution.
Initially following the Android Developer Tutorial, I downloaded the latest versions - 18, 19, 20, etc. When I was creating the project, however, I was specifying much early versions for compatibility; all the way down to 7 or 8. I looked into this because I remembered seeing a message from the IDE regarding the Action Bar and how some commands weren't supported on Version X.
I went back and downloaded all the versions down to 7 or 8 and set the compatibility accordingly. The example now works with minimal other changes. I realize that I may be overlooking something but this is the only major change I made and it seems to have done the trick.
Hopefully this will help other newbies!
Yusif Nurizade
Good day everyone!
I am a graduating student doing Google App Engine-Java Web Application.
My problem is I need to compile/build it so it will run upon click. I've been trying exporting it to a jar file however it outputs no main class.... problem.
I've been looking for other method but internet fails me or maybe i'm not pointing on the right track.
Here's my output whenever I'm using the command line:
its working fine when i'm using eclipse.
Any leads? Sorry if my question is quite silly.
Thanks in advance :))
Firstly you should definitely consider updating your GAE SDK as it seems the defaultZoneTL field was removed from JDK 1.6 U31. Updating the GAE SDK should avoid that problem.
If you can't do that then check http://code.google.com/p/googleappengine/issues/detail?id=6928 and try to implement one of the workarounds suggested. (Essentially launching with -Dappengine.user.timezone.impl=UTC OR -Dappengine.user.timezone=UTC)
I am an app developer, and I recently had to re-install windows, so I lost all of my app data :(
I have the apps on the market, so can get the APK's, but my question is:
Can I decompile them back into eclipse, or will I have to re-make them from scratch?
Thanks for your answers, Liam
Unfortunately, there's not any way to get your source code back from just an apk.
I highly recommend in the future using a source control management system (I use git) and back up online (I use bitbucket).
I doubt very much the APK contain your source, unless you configure your build to include them. So no, you can decompile each class and reconstruct some of the code, but chances are, u have to rebuild from scratch.
This could be a rather crazy question, but I wanted to get some insight on it before I spend all the time trying it.
Is it possible to rebuild framework.jar (like say pulling the framework.jar from MIUI), decompile it to smali and then rebuilt it from scratch (via reading through and remaking it yourself into java)?
I planned on doing that + taking the similar files from Cyanogen mod as a reference to build off of. The reason I was interested in doing all this was because I have a phone that needs the Radio Interface Layer more or less rebuilt and it's just become too much of a hassle to deal with editing the smali directly and debugging it.
I figured I would ask here because people would be less quick to rush to judgment on whether it was possible or not. I don't see why it wouldnt work if you are adding everything correctly (in theory) and rebuilt the classes.dex file in the source after.
Main reason I am asking is part of an effort to port MIUI to my phone. I figured the lesser of too headaches was rewriting the java and rebuilding a working framework.jar (which has parts in it that are not in the CM7 or AOSP sources) than editing the framework.jar that comes with MIUI to work correctly.
While there are various ways to decompile a dex file back into java, none of them will produce java that is perfectly compilable. You would have to spend tons of effort cleaning up the java code from a decompiler, to get it to compile. It's pretty much not an option for something as big as that.
Your best bet is to get something like AOSP or CM working on your phone, so that you can build the framework yourself directly, with whatever modifications you need.