I just tested on an iPhone6 (running iOS 8.1.3) and noticed there aren’t any outputs in xcode’s device console, which now makes it impossible to check for errors.
What am I missing here? With all my other devices (running older iOS versions than 8.1.3) this is working perfectly.
Thx for your help!
Hi Daniela,
Can you search online and see if other users (app developers in general) are reporting this? I just upgraded to 8.1.3 yesterday, using my iPhone5 and Xcode 6.1.1, and I’m seeing all console reports just like before. So the only difference I can see is an iPhone5 vs. an iPhone6, which seems odd, but these things do sometimes occur…
Brent
Hi Brent,
I updated to Corona version 2545 some minutes ago and now it is working. I now can see the Console output like with all the other devices.
But I still have a problem to get outputs for Android devices now… using the adb logcat Corona:v *:s command in terminal is not detecting any connected device. I then googled a little bit and found the Android Studio Application, but it’s only working with the Java Development Kit Version 7.0 and I don’t know if installing the JDK 7.0 is compatible with Corona or maybe a bad idea!?
Do you have some info about this maybe?
Best,
Daniela
Hi Daniela,
For Windows, you need to use SE 6 according to our docs (and not Java 7 on Mac):
http://docs.coronalabs.com/guide/start/installWin/index.html
http://docs.coronalabs.com/guide/start/installMac/index.html
And on the Android Studio thing, please see here:
http://forums.coronalabs.com/topic/54273-android-studio-integration-status/
Brent
Thank you.
So it looks like I don’t need Android Studio if I just want Console outputs for testing on an Android device.
But how can I get Console outputs on an Android device? The following command in the Mac terminal
adb logcat Corona:v *:s
is not working (not detecting a connected device). Is this a known problem? I have activated the developer mode on the device… do I miss something else here? I have a new Android device, but I thought with activating developer mode on the device the command should work!?
What happens when you type:
adb logcat
from the command line???
I already have tried this and it too wasn’t working. Somehow the device can’t be detected I guess because the waiting for device is the last message I can see.
A. try rebooting.
B. There may be some steps you have to do to get the USB driver to recognize the device. You used to have to edit a file and put a hex code in it, but I think Android changed it. But you might want to google around and see what it takes to get adb working with your device. This isn’t a Corona specific thing so there are tons of tutorials out there on getting adb setup properly.
Rob
Thx again for your help. I figured it out finally. I had to install the KIES software from Samsung, so the devices will be detected. Without KIES the connected device can’t be detected and when it is shown (like for example in the Android Studio software) it appears offline.
So KIES was the solution!
Great, glad you solved it.
Hi Daniela,
Can you search online and see if other users (app developers in general) are reporting this? I just upgraded to 8.1.3 yesterday, using my iPhone5 and Xcode 6.1.1, and I’m seeing all console reports just like before. So the only difference I can see is an iPhone5 vs. an iPhone6, which seems odd, but these things do sometimes occur…
Brent
Hi Brent,
I updated to Corona version 2545 some minutes ago and now it is working. I now can see the Console output like with all the other devices.
But I still have a problem to get outputs for Android devices now… using the adb logcat Corona:v *:s command in terminal is not detecting any connected device. I then googled a little bit and found the Android Studio Application, but it’s only working with the Java Development Kit Version 7.0 and I don’t know if installing the JDK 7.0 is compatible with Corona or maybe a bad idea!?
Do you have some info about this maybe?
Best,
Daniela
Hi Daniela,
For Windows, you need to use SE 6 according to our docs (and not Java 7 on Mac):
http://docs.coronalabs.com/guide/start/installWin/index.html
http://docs.coronalabs.com/guide/start/installMac/index.html
And on the Android Studio thing, please see here:
http://forums.coronalabs.com/topic/54273-android-studio-integration-status/
Brent
Thank you.
So it looks like I don’t need Android Studio if I just want Console outputs for testing on an Android device.
But how can I get Console outputs on an Android device? The following command in the Mac terminal
adb logcat Corona:v *:s
is not working (not detecting a connected device). Is this a known problem? I have activated the developer mode on the device… do I miss something else here? I have a new Android device, but I thought with activating developer mode on the device the command should work!?
What happens when you type:
adb logcat
from the command line???
I already have tried this and it too wasn’t working. Somehow the device can’t be detected I guess because the waiting for device is the last message I can see.
A. try rebooting.
B. There may be some steps you have to do to get the USB driver to recognize the device. You used to have to edit a file and put a hex code in it, but I think Android changed it. But you might want to google around and see what it takes to get adb working with your device. This isn’t a Corona specific thing so there are tons of tutorials out there on getting adb setup properly.
Rob
Thx again for your help. I figured it out finally. I had to install the KIES software from Samsung, so the devices will be detected. Without KIES the connected device can’t be detected and when it is shown (like for example in the Android Studio software) it appears offline.
So KIES was the solution!
Great, glad you solved it.