I have been trying to use android studio and every time I deploy an app on a device, it gives me an error saying:
Installation failed since the device possibly has stale dexed jars that don't match the current version (dexopt error).
In order to proceed, you have to uninstall the existing application.
I have tried using Build->Clean Project and yet it seems to do no good.
I have also tried deleting the file from /data/local/tmp on device (as my phone is a rooted one), but, all in vain.
If anyone knows a way out, please, please help.
Uninstall the application from the device.
Check the storage space.
Once Restart the mobile and try to install it
Related
I am just learning react now. I tried to install react app so many times in my Visual studio but It didn't work. It always shows installing required packages and I've waited so many hours with so many tries it didn't worked as well. I have this issue only and Node install 'my-app' folder with simple json file only. Anyone knows what's the problem here?
enter image description here
I tried to update Node recent version but it was already updated. Even i tried Non LTS supoert Node version it couldn't helped me.
I tried different types of package manager like 'npm' and 'yarn' instead of using 'npx' but then I know these package managers supported before node version 5.2 or 5.8, I think.
I searched for this problem in youtube nothing else there.
I used metered network in my PC but when I used WiFi with stable connection also it didn't install.
I tried so many different extensions in Visual studio, I thought it would be help but none happened.
What are the problems here? and What i want to do pls explain to me, bros.
I recently wanted to try React Native to code applications. This requires many installations which worked fine, except for AndroidStudio.
I use a Windows 10 PC, with hybrid hard drive.
I had to download AndroidStudio files on the second drive (D:) because my first hard drive is very small and already full. This type of installation never caused any problems with me (I installed dozens of softwares on D: like this).
I followed diligently React Native Getting Started Guide to install everything on windows for android devices. I ran into several problems :
Firstly, the Android Studio installer never asked me if I wanted a Custom or regular installation. I think this is not an issue as I can still install what's needed afterwards via the SDK manager.
Once I installed everything in the SDK manager and in the AVD manager as asked in the tutorial, I placed the path for ANDROID_HOME in environment variables menu (I also tried in system variables, in both, but this doesn't seem to change anything), and the Path for platform-tools in the Path variable.
One particularity is that I have the following files :
D:/AndoidStudio containing the app (that would have installed itself in C:/Program Files otherwise)
D:/AndroidStudio_sdk containing the downloaded sdk (Android Studio makes it mandatory to install these files in a different folder)
Then, when I clicked on the green triangle from AVD manager to start the emulator, nothing happened, and I received a Notification in Android Studio's IDE :
Emulator: PANIC: Cannot find AVD system path. Please define ANDROID_SDK_ROOT
I tried to add this environment variable pointing to the same location as ANDROID_HOME (D:/AndroidStudio_sdk). This hasn't solved the problems and made a new error pop up instead of the first one :
Emulator: PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value [D:\AndroidStudio_sdk]!
I looked up on React Native website and it appears that ANDROID_SDK_ROOT environment variable is in this case used when there's no SDK files inside the ANDROID_HOME location.
What I can't understand is why I can't find the sdk location ? I tried in SDK manager, but it just gives me D:\20_AS_sdk, which is just the value of ANDROID_HOME.
Another particularity is that I can't find the sdk folder inside D:\20_AS_sdk (or any default route evoqued on different tutorials).
I really don't understand these issues and I've been blocked on this since 2 days, the only useful comments I found on other threads were just :
- set your ANDROID_HOME variable to the proper place, which I already did
- install the SDKs and emulator needed, but I did it too without issues
I tried to remove everything from AndroidStudio and the linked paths and reinstall everything, many many many times unsuccesfully...
Thank you for your support :)
In MonoDevelop when compiling and running an app developed for Android against the simulator, the app compiles then crashes immediately in the simulator with the following application output...
E/mono ( 225): The assembly mscorlib.dll was not found or could not be loaded.
E/mono ( 225): It should have been installed in the `/home/jon/Development/xamarin/mono/BUILD/armeabi/install/lib/mono/2.0/mscorlib.dll' directory.
Keep in mind that I'm not Jon so I don't even know where it's getting the /home/jon path configuration. Though I have found that path in other similar but ultimately unrelated searches on the internet so I imagine it's a path on some other devs machine.
mscorlib.dll is indeed on my machine. located here...
/Developer/MonoTouch/usr/lib/mono/2.1/
and here...
/Developer/MonoAndroid/usr/lib/mono/2.1/
I've tried targetting various Android SDK environments (currently 2.3 and the simulator is currently running under the 2.3 SDK environment as well).
I'm on Mac OSx 10.7.2. Using the latest version of MonoDevelop, Mono and Mono for Android. I've also got the latest MonoTouch installed as well and iPhone apps compile fine if that's worth anything.
The closest thing I can find to a hint at the issue is here...
http://phonicuk.com/Forums/ViewThread.aspx?tid=401
I've tried reinstalling Mono and Mono for Android but admittedly have not tried uninstalling in entirely before a reinstall. I've searched within files for the /home/jon path thinking that it must be a configuration somewhere but haven't been able to find it anywhere.
I found this... Mono return error: mono mscorlib.dll was not found
Along with a few other things that were sort of in the same vein, but ultimately nothing that seems to be a fix.
Any ideas?
Update: From the suggestions in jonp's answer below it indeed seems like the Mono.Android.DebugRuntime package is not installed. So far I've tried a couple of MonoAndroid reinstalls and have tried removing MonoAndroid entirely beforehand. I'm trying to figure out if there is a way to add the package manually, but I'm so new to this.
Another update: Not sure why I didn't try this already, but I created a HelloWorld MonoAndroid app and it works fine. The compilation took a while longer too for that one and I could see if was setting up the required packages, so there has to be an issue with the specific solution.
When you install a Debug build of your app on the device, three .apk files are installed:
Mono.Android.DebugRuntime, which contains libmonosgen-2.0.so, mscorlib.dll, etc.
Mono.Android.Plaltform.ApiLevel_N, which contains Mono.Android.dll for API level N.
Your application.
My guess is that the Mono.Android.DebugRuntime package has not been installed. To check this, run:
adb shell pm list packages | grep Mono.Android
I'm going to guess that it's missing. :-)
Next, why is it missing? When you Run the app within MonoDevelop, all required packages are checked for and installed. It seems rather odd that it wouldn't be. Is your device low on disk space?
adb shell df /data
How are you launching the emulator? If you're launching within MonoDevelop, there should be enough free space to install all of the above packages. However, if you launch it yourself, the default /data size is 64MB, which isn't enough to support a Debug build environment. Please launch the simulator from MonoDevelop and re-Run your app, or launch the emulator so that it has enough free space:
emulator -partition-size 512 -avd YOUR_AVD_NAME
I've found various proposed solutions to this problem on this internet, but none of them work for me. Does anyone know why this might be happening?
http://answers.unity3d.com/questions/15294/xcode-build-and-archive-error-no-such-file-or-directory
http://blog.joshschumacher.com/2011/04/06/xcode4-the-operation-couldn%E2%80%99t-be-completed-no-such-file-or-directory/
I've tried archiving with every combination of coding signing vs not using code signing, and I've tried using every combination of provisioning profiles, but I still get the same error every time.
I'm very confused as to why I'd even be getting an error like this when trying to save a file. I'm using XCode 4, my application builds for archive fine. In fact, I can even upload my application to itunesconnect (and it was accepted!). I just can't create an IPA for sharing and beta testing before submission.
Any ideas?
The error message
Right before I get the error
After much frustration, I filed a developer support request with Apple. The technician I spoke with was able to save my archive as an .ipa on her computer -- the exact same archive that I was not able to save on mine, which pointed to a possible bug in my system (and from the sounds of it, many other people's).
She recommended that I uninstall and reinstall XCode and the developer tools, and that worked!
Here were her uninstall instructions:
Make sure that your machine is running the latest Mac OS X (10.6.7) and iTunes.
Run the following command in the Terminal application to uninstall your SKD:
sudo <Xcode>/Library/uninstall-devtools --mode=all (where <Xcode> is the path to the directory that contains your SDK.)
Drag your <Xcode> to the trash and restart your machine
Re-download and install Xcode (4.0.2) from the iOS Dev Center. Make sure that the System Tools, UNIX Development, Essentials packages in the Custom Install pane are selected before installing it.
I have the same issue after my distribution certificate was expired. I add new ones (private key and certificate) and xCode "Share" command starts to produce such error.
The problem resolves as soon as I remove old private key & certificate from Keychain Access.
Hope it helps
Selecting "Don't Re-sign" at Identity solved the same issue for me.
I actually had the same problem, but a different solution (and reason). I had Xcode 3 and Xcode 4 both running at one point. I recently deleted Xcode 3 and moved my Xcode 4 from /Xcode4 to /Developer directory. This caused me to have the same issue you describe.
I moved the directory back to /Xcode4 and now my archives save out correctly.
I also had the same problem but I could resolve the problem in the below way.
My project was on the portable disk (formatted as FAT-32) and the project referred some folders on the same disk as "add folder reference for any added folder". I could build it any configurations however I couldn't just make .ipa file with above alert.
So, I copied the referenced folders on the portable disk to the desktop of the disk installed XCode (MacOS). And adding again the folders into the project. I could make .ipa file.
I installed Xcode 4.0.2 in one directory and then manually moved it to another.
When I moved Xcode back to the first directory everything worked.
Adobe Air brings following exception:
The application could not be installed because the AIR file is
damaged. Try obtaining a new AIR file from the application author.
Please add the different reasons which may lead to this error.
We had the same error as this guy:
The file ~/.airappinstall contains the following error:
failed while unpackaging: [ErrorEvent type="error" bubbles=false
cancelable=false eventPhase=2 text="invalid package signature"
errorID=5022]
The actual reason was not a damaged file or something like this, but our machine had a date from the past, which was not valid for the given certificate. After correcting the date/time on the computer, the installation worked just fine.
Even I faced the same error=5022, after thinking a lot on this issue, I finally got the
solution for this problem. It is simple, before installing the air app set the correct Date & Time for the system, WALLA it installs smoothly.
No need of changing the png name or anything else.
I faced this problem yesterday because my antivirus (avast pro/silent mode) was blocking access to file until finishing scanning, looks like installer don't like to wait, so when I switched off silent mode I made antivirus ignore scanning the file and installation completed successfully.
I have a virtual drive mapped to S: so that paths are the same between my home computer and work computer. I was trying to install the AIR app from an S: path. I guess it did it like it. Moving app to my desktop and launching there, worked.
Make sure you are signing the Application distributable and distributing the certificate along with the .air file.
I ran into same problems and solved it this way.
I had this issue when using Flash Builder 4, but building a Flex 3 application.
Basically, the installed AIR SDK in the Flex 3 SDK folder was AIR 1.5.3 (if I remember correctly), but the Flex 4 SDK folder had the AIR 2.0 SDK files (I'm not completely what the problem was).
My solution was to download the AIR 2.0 SDK, and unzip it over the Flex 3 SDK folder. Once I did that, the installation file worked fine. There is actually an article on Adobe about overwriting the AIR SDK files this way, although it didn't mention anything about installations or Flash Builder 4.
Mine was failing because I had another app on my system with the same name. Not a version of the app, a completely different app--native, not AIR.
Once I removed that app it worked fine.
For odd installation errors, keep in mind that Chrome uses a version of Flash that does not support AIR badge installation.
I encountered this error when trying to install an AIR file from an external / network drive. Copied the file locally, and installation proceeded normally.