I'm building an android app using Eclipse, and when I want to run/debug it on my android device, it wont run, even if it is just a "hello word" project.
The information shown on console tab is:
"Installation failed due to invalid APK file!"
I'm wondering what was wrong, and how to fix it.
I found this thread that almost had the same problem with yours: Eclipse installation failed due to invalid APK file?
Please apply those solutions first, then get back to me if it's still not fix
You may have made changes to your versions in your Android manifest file. Delete the app from your device and run it again!
Related
I am flowing the official tutorial to install flutter and run the default app on my iPhone Device. After I execute the flutter run, the app is installed and launched on my iPhone but the logs show the bellow error. How do I solve it?
Launching lib/main.dart on My iPhone 6 in debug mode...
Automatically signing iOS for device deployment using specified development team
in Xcode project: XXXXXXXXXX
Running Xcode build...
└─Compiling, linking, and signing... 50.2s
Xcode builds done. 90.1s
Installing and launching... 41.1s
Error launching the application on My iPhone 6. <-- Error Here
It happens that there are some process needed to Flutter plugin correctly run on physical devices. I struggled with that and finally found that the processes idevicesyslog and iproxy were being silently blocked by MacOS.
You may have noticed already a message liked this:
or a similar one for idevicesyslog.
Once I went to System Preferences -> Security & Privacy in General tab and allowed this apps, everything works. Note that this screen shows only the last app that you tried to run. So I'd recommend that you run flutter app with preferences opened so you can (hopefully) see the messages appearing and click allow.
MacOS may warn you one more time about the file being downloaded from the internet. Just click open and you're good.
The error do not show again after reboot the iPhone.
Same error -- Running fine through Xcode, when I ran with flutter CLI, the app would open, but the terminal log output would crash with the error as in the post.
I ran flutter update and simultaneously turned iPhone off and back on. After doing that, the below popup appeared (on mac).
I believe after the install finished, I ran the below (which I ran several times before updating flutter and installing the popup):
flutter clean
rm -rf ios/Pods
flutter pub get
cd ios && pod install && cd ..
run the flutter app using flutter run from command line, then the MacBook will ask for permission to open the app and app runs,
(lldb) warning: libobjc.A.dylib is being read from process memory. This indicates that LLDB could not find the on-disk shared cache for this device. This will likely reduce debugging performance.
Error launching application on device-XXXXX.
Building & Replace with a newest version ios-deploy solved problems list aboved. Flutter SDK bundled a pre-built command ios-deploy in __PATH_TO_YOUR_Flutter_SDK_/bin/cache/artifacts/ios-deploy/, just replace it.
Please reference to: Flutter Error launching application on device issue .
When trying to launch the native watch application from Tizen IDE, I see the strange message "Certain application categories, such as "Watch Application", cannot be launched by "Run As".
Indeed, I try to use Run As from the project local menu to launch my app. But how else I am supposed to launch my application on the emulator?
The emulator device (watch) is up and running, visible on desktop as a separate widget. It is selected. The signing configuration is set up.
On the console output I see the message processing result : FATAL_ERROR [61].
I also tried to launch through the created launch configuration but this results the same error message.
The IDE logs show the following stack trace:
[2015.09.06 12:16:48][ERROR] ConnectionExplorer.java(658) - Fail to get platform log
[2015.09.06 12:18:59][ERROR] RdsDeployer.java(269) - Cannot partially upload or reinstall
org.eclipse.core.runtime.CoreException: [RDS] Cannot install application
at org.tizen.common.rds.RdsDeployer.newCoreException(RdsDeployer.java:699)
at org.tizen.common.rds.RdsDeployer.postInstall(RdsDeployer.java:634)
at org.tizen.common.rds.RdsDeployer.partialZipInstall(RdsDeployer.java:566)
at org.tizen.common.rds.RdsDeployer.deploy(RdsDeployer.java:267)
at org.tizen.nativecommon.launch.TizenLaunchDelegate2.deployApplication(TizenLaunchDelegate2.java:783)
at org.tizen.nativecommon.launch.TizenLaunchDelegate2.launchApplicationForRun(TizenLaunchDelegate2.java:504)
at org.tizen.nativecommon.launch.TizenLaunchDelegate2.launch(TizenLaunchDelegate2.java:216)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: org.tizen.common.sdb.command.message.CommandErrorException:
Error code: FATAL_ERROR
Error message:
Command: /usr/bin/pkgcmd -q -r -t tpk -n com.au.heywatch
Management: Installation or uninstallation is not working temporarily.
P.S. I add "eclipse" tag because Tizen SDK is very clearly Eclipse based IDE. Using Tizen IDE 2.3.1.
Watch face applications(Web/native) are never installed as widgets. You cannot see them in app menu.
Reason:
Within your tizen-manifest.xml file in your project, you'll find below line there
<watch-application appid="org.tizen.watchsample" exec="watchsample" ambient-support="true">
which makes your app as watch application and these apps are known as watch faces because they will be used in setting as the main watch in gear.
And on emulator, you cannot change the watch face on the home screen. Hence, you won't be able to test your watch application that way.
Had the same issue. My problem was certificate setup.
i followed there instructions: http://127.0.0.1:50224/help/topic/org.tizen.addon.certificate/html/dev_env/setting_author_certificate.htm
(link is from help and should work in browser when Tizen IDE is up, alternately you can go to Tizen IDE -> Help -> Help Content and search Certificate.
More specific: Distributor certificate i had was wrong (use the pass received by Samsung by email)
After fixing certificate, don't forget to right click your device in Connection Explorer and click Permit to install applications.
I wonder if anyone has faced the same problem.
When we done some modification on the code, as the emulator is running; is there any way we could see the instant change without closing the emulator?
Sometimes when I made changes on the code then run the emulator, the amendment that I made doesn't seem to show on the emulator even after I clean the project.
Does anyone have any idea how to solve this?
Thanks.
Eclipse has an option under 'Run' in the menu bar to build, and run. This will re-package the application and send it to either your AVD, or attached android phone.
[2011-11-15 22:29:18 - MyAndroid] Failed to install MyAndroid.apk on device 'emulator-5554': device not found
[2011-11-15 22:29:18 - MyAndroid] com.android.ddmlib.InstallException: device not found
What troubleshooting steps have you done?
Has the app been installed on the emulator previously? If so, fully uninstall the app from the emulator first.
Try closing the emulator, and eclipse (if using eclipse). Then restart and try again.
If the issue keeps happening, you may need to delete the 'cache.img' in your AVD directory.
And if that doesn't help, delete the AVD, and recreate it.
I moved my Android project to a laptop and now I get this when I hit Debug. Sounds like this is a bug? This shouldn't happen via Eclipse as far as I know.
Re-installation failed due to different application signatures.
The weirdest thing is this happened after I upgraded sdk/adt and Eclipse to support SDK 2.2 It was working fine earlier, and now it doesn't, so it might be a bug.
It happens because keystores on your laptop and original pc are different. it's called debug.keystrore
and located in %USER_HOME%/.android/ folder. TO be more specific it happens because eclipse tries to push apk with reinstall key. So you have two options
Share debug.keystore between various development pc's
Manually uninstall your apk from device ( using adb )
I also got the same problem and fixed it. you should do the following to fix it,
Uninstall the application from your mobile if you load it
already.
To uninstall goto settings->application->manage application.
Run the application again and choose the mobile
Hope this will help you
After you copy debug.keystore to your PC, you need to rebuild project on PC.
I had the same issue using the Droid emulator. I solved it by uninstalling the package from the application settings in the emulator as you would a normal device. On the next run, it reinstalled and the error went away.
I got the same problem and fixed it by just wiping the user data on the emulator. My guess is that the emulator keeps the project installed unless you wipe the data, so if your new project doesn't match some internal parameters it doesn't like it and won't reinstall it.
I also had the same problem and fixed it by uninstalling the app and reinstall it again.
ah i think i found your answer:
Why does the app signature change in Android after a classpath change?
its changed if you change the classpath
After searching and checking the phone, i came to know that i am currently developing 2nd version of this application which is already downloaded from android market in my phone, now as this app is signed and having different signatures this is throwing the above error.
Now, to resolve this issue, i had just uninstalled the app from mobile and run/install the application again.
I had the same issue with the emulator and i ran the command "adb uninstall TheNameOfPackage". Of course you must first go to the directory where the adb.exe has been installed, usually C:\Program Files\Android\android-sdk\platform-tools, and then run the above command.
For me after I copied all of my keystore files from my machine at home, I had to do a Project->clean. After that it worked perfectly.
When i tried to uninstall the application from my device after this issue occurs, i cannot able to find the app in my device. I don know where it gone. Then i uninstalled using adb,
adb -d uninstall <app package name>
This is the answer who are facing the issue similar to my problem.
I had the same issue.
To fix it I uninstalled the old .apk of the project from my device.
Go to device/emulator Settings -> Apps, find your app and uninstall it.
Or
In Android Studio open tab "Gradle" (on the right side), open:
appName
..appName
...Tasks
....install
.....uninstallAll
and click twice on this task to execute it.
Important note:
If you still get this error after uninstalling, try to Build->Clean Project.
If you still get this error, even if in your device Settings->Apps list you have no this app already, try to Build->Clean Project