iOS Device doesn't show up in XCTest configuration

Answered

Problem

After AppCode updated to 2018.1.5, it is able to run with XCode 9.4 environment. But iOS physical device doesn't show up in XCTest configuration

With XCode 9.4.1

build, run and test work both on simulator and physical device

With AppCode 2018.1.5

build and run work on both.

Test on simulator works fine, but physical device is missing on configuration device list. Tried edit configuration, not help

Workspace

My workspace was created recently with XCode 9.4. It consists of a library project and a sample project. It provides BLE feature which requires physical device to test. So that XCTest locates in sample project, as show in screenshot below

 

Environment

  • macOS High Sierra 10.13.5
  • XCode 9.4.1
  • AppCode 2018.1.5
  • CocoadPod 1.5.0

 

Similar to this post

https://intellij-support.jetbrains.com/hc/en-us/community/posts/206593255-iPhone-doesn-t-show-up-in-Ocunit-configuration?input_string=test%20on%20device 

3 comments
Official comment

Hi,

Could you submit a screenshot of your NotepadKitTests.testVersionInfo run configuration from AppCode?

What if you open NotepadKitTests file in editor and try to run tests from gutter / context (see below), would the run configuration created as a result of that be only runnable against simulator as well?

Sorry for late rely

During the few days, both macOS and AppCode upgrade.

Environment

  • macOS High Sierra 10.13.6
  • XCode 9.4.1
  • AppCode 2018.1.6
  • CocoadPod 1.5.0

 

I tried gutter / context, with no physical device detected, as below

 

I tried cleaning up the repository with "git clean -xdf", which result even stranger

In the beginning, Xcode could not run NotepadKitTest in the "Test Navigator", but run from gutter is OK

After building and running NotepadKitSample APP on the physical device, XCode "Test Navigator" becomes enabled

Nevertheless, AppCode come with no luck. Building and running NotepadKitSample on physical devices is fine, NotepadKitTests is not.

 

 

I'll try to make a public sample repository with the same problem on GitHub later

0

>I'll try to make a public sample repository with the same problem on GitHub later

Thanks, that would be very helpful.
0

Please sign in to leave a comment.