At the time of debug my titanium application, it always say "failed to run dexer" in console and Build fails. Even i am not able to run very basic app in Appcelerator Titanium. I tried to find the solution here and there but did not get able to solve the issue. Every time i am cleaning the project, restarting the Titanium some time restarting my windows machine also but still facing the same problem. Hoping to have some quick solution.
Please Goto Project->Clean
Then restart your Titanium Studio. Detach your mobile device from computer and re-attach and wait for 5mins.
If still doesn't work, then goto your RUN->CMD->adb kill-server->adb devices
Related
So i've downloaded the correct apple silicon android studio installation from their website. when trying to install the installation process gets stuck on this message:
Downloading
https://dl.google.com/android/repository/emulator-darwin_aarch64-8807927.zip
Warning: This download could not be finalized from the interim state.
Retrying without caching. Downloading
https://dl.google.com/android/repository/emulator-darwin_aarch64-8807927.zip
I have left it like that for hours but with no luck
any workaround?
today I solved the problem like this:
Download file and unzip: https://dl.google.com/android/repository/emulator-darwin_aarch64-8807927.zip
Cancel button.
Go to /Users/YOUR NAME/Library/Android/sdk
Delete the folder "emulator" and add new unzipped folder the same name
Finish!
Try to add simulator.
Later, maybe I will find a better way, but this way allowed me to work at the moment and not delay work.
#TomerZigdon Do you actually need an emulator for testing?
Here's a solution that worked for me. I have a physical device that I test the apps on and I don't require an emulator. So as per this answer (https://stackoverflow.com/a/39880185/3273842), I disabled android checking for first run. Android Studio opens just usual and on creating a new (dummy) project, it installs the needed SDK versions (not the emulator)
disable.android.first.run=true
Full credits & steps to follow: https://stackoverflow.com/a/39880185/3273842
This has been resolved by Google via this bug ticket:
https://issuetracker.google.com/issues/242575308#comment27
Verified by bo...#google.com.
hello,
thanks a lot for reporting the problem.
please try to download emulator 31.3.10 again on M1, and it should work now, but report problems if you run into.
thanks for your patience.
I am new to Kony enterprise edition. I tried to run my app using the Android emulator, always its showing unknown error (code 100-ref img), when I click OK, its closing app, I check the Support x86 devices in the settings. I install the apk using cmd, app installed but when I tried to open the app is showing the kony animation with launching icons. I tried to used local host in the kony app but no use. I am unable to guess the what is the error, and what went wrond. Requesting great help to run the app, and kony editor is taking very long period to build in at least in one platform (like android, desktop etc). Its killing my time for building app rather than development. Appreciate any tips to build as fast as possible and track errors.
You can check the error's cause in DDMS(WINDOWS key+R -> DDMS -> press Enter). It should log the message for the cause of your error. Change the debug level to Error if there're too many messages.
As for making the build faster, it's mostly system-dependent, although you can make a few changes that might positively affect build times. Do this: go to your Kony studio's installation folder and find the eclipse.ini file. Open it and change the values of parameters like -Xmx and -XmsMaxPermSize to a higher number. e.g from -Xmx512m to -Xmx1024m. Now restart Kony studio. As an aside, a machine with a minimum of 8GB ram is recommended, with as less programs running as possible apart from Kony.
Lastly, and this is my opinion, Kony preview is basically a sub-optimal feature that's rarely used by any Kony dev I've ever met. You're better off running the final build on a device.
Exact error:
Severity Code Description Project File Line Suppression State
Error DEP0001 : Unexpected Error: -1988945906 TestApp
What does it mean? It seems it isn't problem with application, it works OK on PC.
Version of OS: 1511, Windows 10 for phones 10.0.10586.164
I've experienced the same problem after updating Visual Studio community to Update 2. Typing in CMD (under admin rights) the following command solved my issue:
net start IpOverUsbSvc
Thanks to Agrgg for a good tip ;)
This kind of error happens very randomly and usually it means there was an issue during the deployment of the app. Things to check:
Developer mode is correctly enabled on phone
Uninstall the app from phone, rebuild solution and then try debug again
Check that the architecture for all projects is set accordingly (ARM for debugging on real device)
Sometimes the VS debugger hangs up, so closing VS and kill from Task Manager all VS processes that are eventually running and restart VS may also help.
I had the same error with deploying onto Windows Phone 8.1 device. In my case the problem was in Windows Phone IP over USB Transport (IpOverUsbSvc) service, which wasn't running. The deployment error disappeared after I'd started the service manually.
I had the same problem.
"net start IpOverUsbSvc" didn't worked for me (throws Access is denied Exception).
I have followed following steps to fix.
Start Run (Windows+R), Type: services.msc
Start/Restart Windows phone IP over USB Transport.
For the RPi, I have RPi3 with WIOT (build 14376) this error happens after failed deployment. Just restart VS and it'll deploy ok.
After trying some of the answers already provided and nothing worked, I fixed the error by simply restarting the phone.
After that the error was gone for me.
I had the same issue, and found that in my case it was occurring while the phone was downloading system updates in the background.
App updates/installations from the app Store were also prevented from downloading/installing.
After the update had finished, all was back to working again.
As Windows Phone 10 doesn't seem to make it obvious that it's downloading updates, maybe worth checking this out if you hit this problem.
I had the same error, solution is here: https://msdn.microsoft.com/ru-ru/library/windows/apps/jj863509(v=vs.105).aspx
Look at Checking BIOS settings required by Hyper-V for Data Execution Prevention. You must select "Turn on DEP for all programs and services except those i select" and in my case application deploys successfully.
For me, it was as simple as unlocking the phone so that the computer would have access to it.
I had this issue as well. None of the answers helped me. IpOverUsbSvc was up and runing, phone reset, system reboot, nothing...
The issue was fixed after a Visual Studio "repair": control panel -> Programs and features -> select VS2015 -> Repair
I got a similar error.
The reason the error occurred for me was because I forgot to add the new splash images in assets after deleting the old ones.
The solution was to add the images. To get the correct image names and sizes, I used this extension for visual studio.
For Windows 10 (desktop) users
I faced this problem after I uninstalled Windows 10 SDK. It deleted the IpOverUsbSvc service from the system.
Solution
Download the Windows 10 SDK .iso installer
Inside it there is Installers folder.
Find Windows IP Over USB-x86_en-us.msi. Install it. (Don't worry if there is no setup window, it installs fast and silently).
I didn't even have to reboot VS2015, it just worked.
Check if the IpOverUsbSvc service is running
Open a Powershell prompt and type Get-Service -Name *USB*
Or go to the Services window. There you should see the IpOverUsbSvc running.
So, I think I get the trick. After plugged in your Windows Mobile device, Windows App Deploy can see W10M device, but once your device goes to lock screen, WPD can not detect it anymore.
You should to plug out and plugin again, with screen unlocked, to make it detectable. (I'm not a really English speaker).
I am currently trying to debug a blackberry application on a real device.
I find the setup time to be ludicrous!
Here is my workflow:
Uninstall the application using Blackberry Desktop Manager (BBDM)
it takes about one minute to select the options to uninstall the app...
BBDM needs to connect to the device and load the application list
you need to find and uncheck the application
BBDM takes about 30 seconds to uninstall the application and its submodules
the blackberry bold 9700 now spends 2 minutes rebooting...
Use eclipse to start debugging
eclipse installs the app
wait for the debugger to attach itself to the device
Start the app manually
All in all, a single debugging run can take more than 10 minutes to execute.
If I miss a breakpoint, I have to start all over again.
Is there a way to optimize this workflow to make debugging on a blackberry device more efficient ?
You don't need to uninstall the application. When you redeploy, it will simply replace the previous version with the new one. Unfortunately it won't avoid the reboot - that's something you'll just have to live with. The good news is that reboot times are getting better on newer devices - it only takes about a minute for my Torch 9800 to fully boot up.
One can only hope that RIM will bring the "hot swap" capability of the simulators into the actual devices.
If you do not use Peristance and the application is not running, you can remove it and then reload it without a reboot.
Furthermore, rather than using the application manager you can use the javaloader.exe file that comes with the eclipse sdk, its located in the bin dir of the sdk to remover or load the cods
Example .bat file
cd C:\Program Files\Eclipse\plugins\net.rim.ejde.componentpack6.0.0_6.0.0.29\components\simulator
java -jar "C:\Program Files\Eclipse\plugins\net.rim.ejde.componentpack6.0.0_6.0.0.29\bin\SignatureTool.jar" -a -c -p myPassword *.cod
"C:\Program Files\Eclipse\plugins\net.rim.ejde.componentpack6.0.0_6.0.0.29\bin\javaloader" -u load myCodFiles.cod
Also personally I debug with the JDE because it is much less laggy then eclipse, but that is a personal choice.
There is some trick to make debugging more efficient in eclipse.
1.You must create fake empty project.
2.And start debugging for it instead of your real project.
3.When debugger has attached, you can run real application on device and debug it without rebooting.
I am using Debug as-> Blackberry Device to debug the application on my Blackberry Torch 9800. It is doing OK most of the times although I admit that debugging in blackberry is not as fast as in iPhone(much faster) or Android(just fine).
I am trying to debug my Windows Phone 7 app, and I am getting the following error upon launching the app in the emulator (via VS2010 debug):
Unable to start program
'\Windows\tashost.exe\'
The drive cannot locate a specific area or track.
Any ideas as what may be causing this? The most recent change I made was adding functionality to save game data, via the IsolatedStorageFile. However, it was working for a while with this functionality in there.
I found the problem. If only I had read the release notes. For anyone else that might be experiencing this issue, it is addressed in the WPDT Beta Release Notes.
Release Notes - WPDT Beta 7/16/2010
Unable to start program error if
project not configured to build or
deploy. If a project is not configured
to build and or deploy a game, the
operation will fail with the following
error message:
Unable to start program
'\Windows\taskhost.exe'.
The drive cannot locate a specific area or track
on the disk.
To set a game project to
build or deploy: In Visual Studio 2010
Express for Windows Phone, click
Tools, then click Settings, then click
Expert Settings to enable the Solution
Configurations drop-down. From the
Solution Configurations drop-down in
the standard toolbar, select
Configuration Manager. Check the Build
and Deploy checkboxes.
what worked for me was to update my graphic card driver. Even though my computer said the device was up to date, going to the manufacturer website and downloading the latest drive allowed it to work. (using Nvidia by the way) this was after after about 5 hours of trying to figure this thing out.
also make sure you all the rest of your updates are up to date, and that directX is current.