I've encountered this error the second time today. For a while I'm able to build an APK (then I switch to dektop kit, then I switch back), and now I'm unable to build with this error:
Android deploy settings file not found, not building an APK.
first time I solved this by deleting the projectroot/android directory, deleting .user file and recreating those.
eventually it got broken again
now I switched from 5.14.1 to 5.12.7, it solved the issue, maybe temporarily, we'll see...
so my question is what that error message means, which file is the deploy settings file, which process puts it there, and which process deletes it and why?
Thank you for your answers in advance.
Restarting Qt Creator solved this issue for me
Related
Seems my Android studios isn't working as it used to work before.
When I run the emulator, it loads for a bit of time, later it opens the emulator, but the project isn't loading up. I'm receiving strange type of error:
Installation failed with message Invalid File: C:\google-services-master\android...\app\build\intermediates\split-apk\debug\slices\slice_2.apk.
It is possible that this issue is resolved by uninstalling an existing version of the apk if it is present, and then re-installing.
WARNING: Uninstalling will remove the application data!
Do you want to uninstall the existing application?
I had some thoughs maybe the project is broken, so I made a new one. The same problem occurs, I created a new emulator, didn't helped either, rebuilded and cleaned the project and still receiving the same problem.
I've checked these topics:
Installation failed in android studio
Android Studio: Application Installation Failed
Couldn't fix it either.. Idk, maybe I should reinstall Android Studios? But hell yeah, it takes so long to install all the updates..
P.S. The project consumes only 1 layout and 1 imageview.
Everything was working fine until now..
I get this error when I open my app:
Installation failed with message Invalid File: C:\Users\wlgus\Desktop\Android\Asimplegame_ver4 (2)\app\build\intermediates\split-apk\debug\slices\slice_6.apk.
It is possible that this issue is resolved by uninstalling an existing version of the apk if it is present, and then re-installing.
WARNING: Uninstalling will remove the application data!
Do you want to uninstall the existing application?
I don't know what I can do to fix this error. I already download apk but it didn't work.
The answer to your question is right here.
Method 1 : Try to clean, rebuild, and run the app.
If it doesn't work
Method 2 : settings>build,execute,deployment>instant run>Enable instant run to hot swap code /resource change on deploy(unchecked this option)
This is likely because the debug key in android studio is different from the one you used to install the app previously.
Are you by any chance installing it from a different computer?
Deleting the build directory (app/build) and then re-building the project worked for me. Try this too, if previous answers fail to resolve the issue.
I'm having an issue suddenly with the export process in Eclipse for licensing my Android app prior to release.
When I build normally under debug mode and deploy to the device, the file size is 11,782Mb. When I use the export process, the file is smaller, 11,322Mb. The file is corrupt and won't load when I test it on the device. When this process is successful, the file is the same size.
This happened once or twice before, and usually cleaning and rebuilding the project sorted it out, but now it's happening every time no matter what I do. Any ideas what is happening here please?
Edit: Production key is fine, use it all the time.
When I attempt to install the app, I get ClassNotFoundException:
java.lang.RuntimeException: Unable to instantiate application com.myapp.android.App: java.lang.ClassNotFoundException: Didn't find class "com.myapp.android.App" on path: DexPathList[[zip file "/data/app/com.myapp.app-1.apk"],nativeLibraryDirectories=[/data/app-lib/com.myapp.app-1, /vendor/lib, /system/lib]]
There are several possible reasons for ClassNotFoundException that I have run into. Here are a few suggestions:
You mentioned "clean and rebuild" - for some reason (usually related to compiling the R.java file) I occasionally need to "clean" more than once for a good production build. I can even do a "clean" and export on a test that is fine, then do an export with a fail. I've probably done over 1000 deployments to Google Play across 50+ apps. It happens...
Android's Installer is corrupt. Yes - this happens, too. Sometimes with a production deployment (not with "debug" or "AVD" - but with "ADB" install or production installs) the Android installer will not ever install your app again. Factory reset of the device is the only solution. I believe an Android OS update can solve the problem, but I've only seen that work intermittently and haven't really tested it.
Manifest errors. Sometimes the production manifest file doesn't match the app classes. Usually this happens with a refactoring of class names. Eclipse in particular does not seem to always modify the manifest file properly. You may need to check it manually.
A res file changed. Sometimes when editing an XML document you will have an error that is not picked up by the compiler or IDE. You do a build and deploy to a test device that for some reason doesn't seem to use the resource or some other strange error. Usually it won't deploy anywhere properly, but I've seen it deploy to a test device and then not deploy in production. As a practice, I avoid this problem by occasionally "uninstalling" and then re-installing the app during testing.
The OP reminded me of another along the lines of the comment below (for future readers) - try deleting the generated files from the build. For example, anything in "BIN" and "GEN" can be deleted and re-built using "build." These files sometimes contain artifacts from previous builds that are no longer valid but are not detected during an automatic build process.
Those are some suggestions. Give them a try...
I recently updated to the most recent Android Studio version (0.2.x), and I am experiencing an issue where I cannot build the project. I receive an error message stating:
Gradle: Execution failed for task ':TestApplication:compileDebug'.
Compilation failed; see the compiler error output for details. C:\Users\user\AndroidStudioProjects\TestApplicationProject\TestApplication\build\source\r\debug\com\example\testapplication\R.java
Gradle: error: illegal unicode escape
Now, I understand I was supposed to reinstall Android Studio as per instructions:
Windows users: Do not install Android Studio 0.2.x in the same location as 0.1.x.
Doing so may cause errors such as ClassCastException or other unexpected behaviors.
It's best if you remove your previous version of Android Studio 0.1.x.
And I actually did, I uninstalled Android Studio, and deleted the remaining folder (Which is apparently not deleted after uninstall) stored at: C:\Users\user\AppData\Local\Android
I then proceeded to clean the registry entry just in case (I tried this on my 3rd attempt after not getting it to work), and rebooted before re-installing.
After the PC rebooted, I proceeded to do a fresh install of Android Studio, it installed successfully. I created a Test Project from scratch (to make sure it was not a problem with opening previous projects), but right after it opened the project it's already showing the build problems. I tried running it and it simply won't compile.
What's even more strange is that all of the problematic lines according to the compiler output are commented lines in the R.java. Here's one:
/** From: C:\Users\user\AndroidStudioProjects\TestApplicationProject\TestApplication\src\main\res\values\dimens.xml
And it points to the character 30 of that line, which is right between the u and the s of the word user (image attached). I actually tried deleting the comments, but as you'd expect the R.java was generated automatically when I asked for the project to be rebuilt.
I have absolutely no clue what the problem is, any ideas?
Known issue. We have fixed it internally already. Should have it out very soon (couple of days max)
I had the same problem and I was using a path similar to yours.
What I did was move the project to the root of the C drive, so the path doesn't start with "C:\Users\user" anymore and the problem is avoided... Not really a solution, but a workaround.
PS: This is not really an answer, but I don't have enough points to comment yet and this might help someone.
I have an issue where every time I try to run a project (that has normally run before), eclipse tells me I have compile errors. There are no errors in the code, the console is empty and I haven't changed anything in the build path...recently. I can actually export the application and install it on the phone and it runs fine, but playing from Eclipse if broken for some reason. I wish I could give more info, but there is nothing to show :/
EDIT: I can't even run a new project. I just tried to make a Hello World app and it still says I have compilation errors. I don't know if this might help so I figured I would add it.
EDIT 2: Problems tab stats this: "Description Resource Path Location Type Error generating final archive: Debug Certificate expired on 3/30/12 10:10 AM TestApp Unknown Android Packaging Problem."
FIXED: debug.keystore issue fixer upper
Help?
Go to window --> preferences --> Android --> build, see where Eclipse points to your debug.keystore, go there delete it, and relaunch Eclipse.