When i try and run the emulator I'm getting the following....
Deployment failed because an app with target platform ARM cannot be deployed to Emulator 720P. If the target platform is win32/ x86, select an emulator. If the target platform is ARM, select Device
Any ideas? I've tried to adjust the configuration to X86 to no avail?
let try to change the value "ARM" to "x86" by BUILD -> CONFIGURATION MANAGER
Batero is correct. But also, note that you Configuration Manager allows you to have separate build targets depending on the profile you are building with.
So you could configure it to build x86 when you are in Debug mode and ARM when you are in the Release mode.
Related
Migrating my native script application to 8.1.5 version.
Fixed the errors that occurs when migrating the native script application.
Application build successfully in the emulator. After build successfully getting error in the application.
How to fix this issue?
Try this:
Go to AVD Manager, and click wipe data on the selected emulator:
Restart your machine (adb connection might be lost).
Then restart your project by running:
ns clear
ns run android
If that doesn't open the app on the emulator, run:
ns devices
Spot the emulator ID you want to run the app on
ns build android
ns deploy --device EMULATOR-ID
Note:
Make sure you've done all 4 blue steps in the cli message (in blue).
i just created a react native project on windows, using expo. After Creating the project i ran npm start and then expo start the next logical thing to do is to press the a button which will launch, the project on the android virtual device, but instead it gave me this error Couldn't start project on Android: Error running adb: Error running app. Error: Activity not started, unable to resolve Intent { act=android.intent.action.VIEW dat=exp://192.168.43.148:19000 flg=0x10000000 }
when i tried running it on my android phone with the expo android app it ran smoothly, i don't know what to do please help thanks
I had the same problem and I got it fixed as follows:
Go to SDK Manager in Android studio > SDK Tools and check whether there is any update for Android SDK Build-Tools. If there is any, please make sure you update it.
Close any Android virtual device currently running and then go to Android Studio Virtual Device Manager and wipe the data of your Android virtual device.
Make sure you have enough internal storage allocated for your Android virtual device to install apps.
Check whether Android Debug Bridge utility is installed in your device. If not please install it. To install in mac, I used the below command (Assuming that you have HomeBrew installed in your mac device):
brew install android-platform-tools
Start your Android virtual device ( This step should be done before running the expo development server)
In the Developer options menu of your Android virtual device, make sure USB debugging option is enabled.
Finally, try running the development server by expo start and press on the button to run on your Android emulator.
I've built my application as an x86 native app, and I've ran it on Genymotion. The problem occurs when I try to debug from Eclipse. In the console view, I get the age old:
gdbserver output:
run-as: exec failed for lib/gdbserver Error:No such file or directory
Verify if the application was built with NDK_DEBUG=1
It all works fine with ARM builds though. I checked that the x86 gdbserver is getting included in my .apk lib/x86/gdbserver. I've also read that the x86 versions of android include a gdbserver locally anyway, so not sure what the point of all that is.
I've been able to manually attach the included gdbserver using adb shell, and then get Eclipse to attach to it remotely using this is a starting point: How to get ndk-gdb working on Android?
It doesn't mention anything about x86 or Genymotion though. Unfortunately, it's tedious, and it's seemingly useless since it doesn't load any symbols (though that's probably because of my ignorance.)
Is there any guidance for making this setup, using Eclipse and Genymotion to debug native apps, work?
Sadly, this is due to a bug in Genymotion v2.2
It will be fixed on our next release (I work for Genymotion).
You are right, gdbserver is not deployed from the apk, and this is why it doesn't work.
You can find here a patch to apply that will fix this apk deployment bug for Genymotion KitKat devices created with Genymotion 2.2: native-debug-fix.kitkat.zip
Warning this patch is only for:
Kitkat (Android 4.4.2) devices
created with genymotion v2.2
Don't apply the patch on other devices, it will brake things.
to apply the patch, simply drag n'drop the zip file on genymotion.
I am using JDeveloper 11g Release 2. I am trying to run a helloworld code on the Android simulator. But i end up having the following error in the console. This is due to some settings that i have failed to set. Can someone help me to add the settings so i could run the app on the Android Console.
The following Android preference configuration is missing or invalid. Set these options in JDeveloper Preferences on the ADF Mobile panel:
Key and Keystore Password
Android SDK Location
Android Platform Location
(oracle.adfmf.framework.dt.deploy.android.deployers.ValidatePreferencesDeployer)
If you haven't keystore for signing android apps right now as for testing purpose. You should select build mode to Debug rather than Release mode.
Application > Application Properties > Deployment > select your android build profiles or create a new one > Click at Edit button > Android Option > Change Build Mode to Debug
You need to install the Android SDK for Android development and Xcode for iOS development.
FAQ for ADF Mobile: http://www.oracle.com/technetwork/developer-tools/adf/learnmore/adfmobilefaq-1866697.pdf
Here you can find the setup guide for Android :
http://docs.oracle.com/cd/E18941_01/tutorials/MobileTutorial/jdtut_11r2_54_2.html
And the one for iOS :
http://docs.oracle.com/cd/E18941_01/tutorials/MobileTutorial/jdtut_11r2_54_1.html
For Android, make sure your emulator emulates version 4.0 or higher in order to avoid :
The Android emulator emulates ARMv5, which is not supported. The emulator must support ARMv6 or newer
If there is also an error above this stating that it can't write the cwallet.sso try closing Jdeveloper and running as administrator.
I tried to run the directx samples from ..\Windows Mobile 6 SDK\Samples\PocketPC\CPP\win32\directx\d3dm\tutorials on a Samsung Omnia and on the emulator and it doesn't work because of a deployment error.
I am using Microsoft Visual Studio 2008 and have installed Windows Mobile SDK Standard and Professional refresh.
The device is correctly plugged in and set up for active sync (I know this because other samples work, also a creating Win32 smart device application and running it works).
When I try to run a directx sample application it compiles without errors but the message:
" There were deployment errors, Continue? Yes/No" appears
If I manually copy the application from the debug folder to the device and run it from there, it works.
The same deployment error message appears if I try it on an emulator. Other applications are deploying successfully.
Is there any way to make the deployment work? Maybe there is an obscure option I need to set...
What I do is:
Connect the Mobile device to the PC,
Open Visual Studio 2008,
Open a directx sample project,
Click Run (in Debug or Release mode).
The problem with the deployment is that the file msvcr80.dll could not be found.
It was specified at the deployment options as an additional file "Project->Properties->Configuration Properties->Deployment" then "General->Additional files"
with the paths msvcr80.dll|$(BINDIR)\$(INSTRUCTIONSET)\|%CSIDL_WINDOWS%|0;
Removing it makes the deployment successful. I have only tested this on a Windows Mobile 6.1 device and with the D3DM reference driver on an WM6.1/WM6 emulator.
What I haven't figured out is where does $(BINDIR)\$(INSTRUCTIONSET) point to.
Also I don't know why msvcr80.dll is in the addition files if it is not actually needed.
Is there actually a msvcr80.dll compiled for Windows Mobile platform on an ARM cpu?
I was able to resolve this issue after doing some low-level Sysinternals Debugging. It was trying to deploy NETCFv35.Messages.EN.cab to the device and in my case it was deleted for some reason. Re-installing .NET CF fixed the issue for me. Wish VS 2008 said what file was missing instead of a generic message. Hope this helps you too.