Run on device : where is my device ?

Hi, I want to debug on my iPhone, my problem is that in the devices list I only have "Not Selected". How to make AppCode detect my device ?

14 comments

It's very strange. Please start AppCode, attach device and then send us AppCode log (~/Library/Logs/appCode10/idea.log)
Also please check if process named AMDeviceService is running when you select iOS as a platform in Run Configuration settings.
What about your setting? Is your mac 64 bit?

0

Here are my logs. I don't see any AMD process, but my Mac is not 64 bit, it's an old Mac Book Pro with a Core Duo, I run Snow Leopard but 32 bit, not 64.
I already had a problem with the filewatcher of AppCode that was compiled only for 64 bit (and now it works perfectly)



Attachment(s):
idea.log.zip
0

That's the problem. AMDeviceService is compiled for 64bit only. Here is a universal binary. Please put here Appcode.app/bin/AMDeviceService and test.



Attachment(s):
AMDeviceService.zip
0

Ah, thanks for this.  I also have an older Mac and this fixed my device detection issues.

0

Well, it runs the app on the device, but whenever I hit a break point AC throws this exception:

Cannot access memory at address 0x10000001b: Cannot access memory at address 0x10000001b
com.intellij.execution.ExecutionException: Cannot access memory at address 0x10000001b
    at com.jetbrains.cidr.execution.ExecutionResult.get(ExecutionResult.java:50)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver.executeCommand(GDBDriver.java:1285)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver.getFrames(GDBDriver.java:809)
    at com.jetbrains.cidr.execution.debugger.OCDebugProcess$OCExecutionStack.<init>(OCDebugProcess.java:927)
    at com.jetbrains.cidr.execution.debugger.OCDebugProcess$OCSuspendContext.<init>(OCDebugProcess.java:900)
    at com.jetbrains.cidr.execution.debugger.OCDebugProcess$BasicBackendHandler$2.run(OCDebugProcess.java:646)
    at com.jetbrains.cidr.execution.debugger.OCDebugProcess$MyCommandProcessor.consume(OCDebugProcess.java:469)
    at com.jetbrains.cidr.execution.debugger.OCDebugProcess$MyCommandProcessor.consume(OCDebugProcess.java:466)
    at com.intellij.util.concurrency.QueueProcessor$2.consume(QueueProcessor.java:101)
    at com.intellij.util.concurrency.QueueProcessor$2.consume(QueueProcessor.java:97)
    at com.intellij.util.concurrency.QueueProcessor$3.run(QueueProcessor.java:191)
    at com.intellij.openapi.application.impl.ApplicationImpl$7.run(ApplicationImpl.java:428)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:680)
    at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:137)
Caused by: com.jetbrains.cidr.execution.debugger.backend.gdb.GDBCommandException: Cannot access memory at address 0x10000001b
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver.throwGDBError(GDBDriver.java:1017)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver.sendRequestAndWait(GDBDriver.java:1009)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver.access$1300(GDBDriver.java:34)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$24.run(GDBDriver.java:814)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$24.run(GDBDriver.java:809)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$30.run(GDBDriver.java:1312)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$2.consume(GDBDriver.java:99)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$2.consume(GDBDriver.java:97)
    ... 11 more



com.jetbrains.cidr.execution.debugger.backend.gdb.GDBCommandException: Cannot access memory at address 0x10000001b
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver.throwGDBError(GDBDriver.java:1017)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver.sendRequestAndWait(GDBDriver.java:1009)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver.access$1300(GDBDriver.java:34)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$24.run(GDBDriver.java:814)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$24.run(GDBDriver.java:809)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$30.run(GDBDriver.java:1312)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$2.consume(GDBDriver.java:99)
    at com.jetbrains.cidr.execution.debugger.backend.gdb.GDBDriver$2.consume(GDBDriver.java:97)
    at com.intellij.util.concurrency.QueueProcessor$2.consume(QueueProcessor.java:101)
    at com.intellij.util.concurrency.QueueProcessor$2.consume(QueueProcessor.java:97)
    at com.intellij.util.concurrency.QueueProcessor$3.run(QueueProcessor.java:191)
    at com.intellij.openapi.application.impl.ApplicationImpl$7.run(ApplicationImpl.java:428)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:680)
    at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:137)



So...no.  Debugging isn't working.

0

It seems better, my iPhone is now detected but the application do not start on it, I only have quickly a Process finished with exit code 0

0

Please replace your log.xml (AppCode.app/bin/log.xml) with this one and send your log once again. thanks.



Attachment(s):
log.xml
0

Can I just submit it via AC's submission system?  I'd rather not post it to the boards.

0

You can use YouTrack (http://youtrack.jetbrains.net/issues/#newissue=yes) to submit the issue and attach the file so that only AppCode developers are able to see it.

0

Finally I restarted completely my computer and the application started correctly, so you can consider this as fixed, thank for your help.

0

what about debugging the app? Does it stop on breakpoints and show variables?

0

Please sign in to leave a comment.