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?
Related
When running an app via Flutter run or VC, we see the flutter console log of the app.
Is it possible to send keyboard events from the developer PC to the app via STDIN which we receive in the app (without VM extensions).
The idea is to use this during development to trigger certain actions in the app.
I ended up building a simple TELNET server into the app. This I way, I communicate with the app running on a phone for debugging purposes.
In the Samsung Smart TV menu there is an option to "Start receiving Smart TV logs". It's "OFF" by default.
When I clicked it I received a prompt to "Check the Console View". I opened the console view and ran the app on emulator, but i couldn't see any logs there.
I know that when the emulator is launched, a separate window showing all the alert(".."); logs is also launched.
I want to know how to use of this option of viewing logs via Console View. I'm new to Eclipse and Smart TV SDK. Is there anything that I'm missing?
How is this different from the logs that are already being shown with the emulator
The console log is used for debugging in real devices.
Emulator already have it's own debugger console window so the emulator not sending anything to eclipse.
If you want to work with real devices this feature is very useful. Do app sync from TV to your workstation and enable the log receiver. When your synced apps run in the real devices (TV/BDP) the alert from application will sent to eclipse's console window
The app will send its logs back to an active eclipse console on the system from which it downloaded the app.
I'm working with eclipse on windows, so I gave my pc a static ip address and installed the Apache 2.2 web server. After uploading my app, I enable the console and open the console view as you did. Then, I start my app, and I see all the log information in the console.
I find this log information essential, because some services return an error in the emulator, but actually execute successfully on the tv. Many of these services are interacting directly with the tv hardware, and there is no other way to debug them.
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 have created a web application using the Google Web Toolkit that is able to receive some data by a mobile client via Http Post. The transmission of the data works well and also the server / client communication using GWT RPC is no problem at all.
However, I need to debug the webserver when receiving data from the mobile device. As I am using Hibernate and MySQL within the web application I do not use the Google App Engine. So if I deploy the web application in local host mode it is only accessible on the localhost:8888.
Now, if I send data from the mobile phone, I have to send it to the locally assign IP address as the localhost of the mobile phone emulator is not the localhost of the computer, where the web application is running. To ensure that everything works, I tried to do some posts outside the emulator (on the machine the emulator is running on). This works, but how can I post from the emulator to my web application?
How can I get access to debug my system? I've already tried to deploy the final application to a tomcat server and use remote debugging, but that fails too.
Best regards,
Florian
Well if I understand your question correctly, the real problem isn't debugging the app on the servlet, the real problem that you're looking at is debugging from a mobile phone. When the mobile phone hits your local network (I'm guessing you're pointing at 192.168..?) you are accessing the compiled GWT code that does not communicate with the debugger.
Put another way, when you debug locally using a browser, you are actually not running compiled GWT code, but instrumented code that is executed with the GWT Debugging Plugin, that happens to work exactly like compiled GWT code. (mostly). So while your local version has "?gwt.codesvr=127.0.0.1:9997" or the like, your mobile phone version cannot do the same, and cannot thus communicate with the debugger.
The best that I've been able to do is to use logging extensively. If you're using an iOS device and change the settings are your safari, it can output logs for you from mobile safari. Also, if you're using the Android debugger with a WebView app, you can attach a listener for log messages and then ferry them on to the ADB and view those in Eclipse. Definitely not as good as a debugger, but that's the best I've come up with so far, and if anyone has a better solution I would love to know it :)
Hope that helps!
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.