I just deployed my app to my iPhone for the first time. Every time it launches it vibrates before running, and it runs fine. The build is a Debug | iPhone one of my app.
Any ideas why it vibrates when it launches and how to stop that? It's definitely not something I coded up and I don't have any exceptions or issues when running in the simulator.
The vibration happens when you build the application in debug mode, and run the application without a debugger waiting. The MonoTouch soft debugger vibrates to inform you that it couldn't find the debugger.
Running the app in Release | iPhone mode solves this.
The number of vibrations is used to notify the user of a problem setting up debugging at startup. The full list (that will be maintained as we expand or modify it) is here:
http://monotouch.net/index.php?title=Documentation/Debugging
As of today:
Device Diagnostics
An application compiled with debug mode that has been deployed on the iPhone will try to contact MonoDevelop on startup on the IP address and port that MonoDevelop had at the time of the build.
If there is an error setting up the debugger, it will vibrate one of more times:
One vibration: The application was compiled with debugging support, but it is unable to reach MonoDevelop on the specified IP address and port to setup stdout/stderr
Two vibrations: It is unable to parse the address configured.
Three vibrations: Could not setup stdout/stderr to the application.
Related
Let's say I'm connected to an actual device, making multiple changes to my app and hot-reload/restart is doing its thing and life's all good. Once I'm satisfied with changes I hit the stop button.
Now, if I pick up the phone and launch the app - it will be an older version of the app that doesn't contain the changes just implemented.
In order to get most recent changes I have to uninstall app from the phone and then go back into the IDE (VSC) and run the app once more to get the latest changes.
Is there a configuration setting that allows you to avoid having to do this?
It is my understanding that while you are developing, and hot-reloading/restarting, you are working on the Dart Virtual Machine. So if you don't make a full build and install the APK on your device then once you close the development build you are working on the VM closes and the code that was running on it is lost.
To answer your question, there is no configuration that you can set to have what is running on the VM to be on the APK without a full build.
This issue has been bugging me a lot lately. I am working on an app that connects with external accessories and sends the data to server. I need to look at the console logs to make sure data being sent is correct however i can not attach the device to mac when I accessory is connected. How can I see console logs after I am done using the app?
I coded an app which starts at the system start up and starts a service which is written in the code. The code is working fine and the service is getting started when the app is installed on a real android device but not on an emulator. I do not have a real device always handy. Any idea how to simulate a start up in an emulator?
I just found a way to simulate a start-up without having to stop-and-start the emulator. Go to the DDMS perspective (if you are using Eclipse) and "stop" the android.core process. This process respawns (you would know this if you have ever owned a HTC where that essential process seemed to stop wayyy to often) and that process of respawning will effectively reboot the emulator- i.e the BOOT event is fired.
Starting emulator simulates a boot up. Didn't know it earlier as I was missing the Toast which I had put up on the boot up for some reasons I don't know. When tried on a faster machine, the same code worked like charm. :)
For some reason, I'm no longer able to connect and deploy to my wp7 device. Zune does not show the phone as being connected, despite the fact that it is connected and the phone shows that it's being charged ... and the wpconnect tool gives the following error:
Failed to connect to the device.
Ensure that the device is completely
booted and is connected to the PC.
(0x80070103)
I rebooted the phone, and I've deployed to it before, so it's definitely developer unlocked. I verified that my computer has internet access. Any other troubleshooting thoughts?
Hey, I run into this all the time. Simply restart your phone and connect again. Make sure you plug in and unplug the phone several times, waiting at least a minute if it doesn't work.
In short, it's temperamental, Keep trying.
Make sure that you have switched off WiFi and Bluetooth on your phone.
I have found that I cannot deploy when Wifi and Bluetooth are switched on - even though Zune is syncing music and other content in the usual fashion. The error messages are frustratingly unhelpful!
As a short term workaround try using the Application Deployment utility to deploy the xap file.
I had the same issue. When I changed the Project properties target OS to 7.1 it worked.
I had the same issue. Only restoring to the previous OS version helped me.
Also I would that it usually happens when internet sharing is turned on.
I think I finally found the problem!
When I had this problem a few days ago, I had been charging my phone (Lumia 900) using a faulty charger which keeps on getting disconnected. And now that I've changed the cable and charger, it started working again!
I had the same problem with my previous phone as well (HTC Mozart), and I had a bad cable back then, but never made the connection (geddit?) between the problem and the cable...
My theory is that when the phone is running on bad power supply/not getting enough power, it sets a flag in the registry, which throws that error.
Also, bizarrely I just found that if you have internet sharing turned on then it won't let you connect.
Any of above mentioned did not work for me. I had many different error messages (included the 0x80070103)
What did is this:
Go to https://dev.windowsphone.com, uregister your phone.
Launch registration tool ("C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Tools\Phone Registration\PhoneReg.exe")
Unregister in tool from 2) too (if it is showing still as
registered).
Now disconnect phone and connect it again
Register phone in tool from 2)
I'm working on an app and I've been able to successfully debug it using the device. I have a crudely working version of the app and I wanted to test it out on the phone, show it to friends and get opinions. The problem is, after doing adb install I now have the icon on my phone but when I try to launch it, it gives me the "Waiting For Debugger the process is waiting for the debugger to attach" message. I have removed the 'debug=true' flag in the application manifest and also turned off usb debugging on the phone. Why is the application thinking I'm still debugging it? What do I need to do to be able to run it without having debugger on eclipse attached?
First, Set debug="false" in manifest.xml, and uninstall application from your device and reinstall it. It will work
just restart the device, not power off, choose restart
If all the above doesn't work, start the application in debug mode.
1) In eclipse -> go to the debug perspective
2) When the app is running -> press the "Disconnect" button (next to the "stop")
3) Turn off your phone.
4) Remove the battery for 30 sec
All should be back normal