After new iOS/Xcode update - Running app returns immediately in AppCode Follow
When trying to launch app, it build successfully, but immediately returns and prints
'Process finished with exit code 0'
to output when running.
Running through Xcode works fine.
It seems like the most recent Xcode + iOS + OSX update caused this as everything was fine before.
Any information on how to solve this would be greatly appreciated!
Please sign in to leave a comment.
Xcode compatibility for AppCode 3.3.3 is limited to the Xcode 7.2.x version max (please read this blog post for details). Support for the current Xcode 7.3 will be delivered in 3.4 EAP builds. Please try using it and sorry for the inconvenience!
Sorry for the inconvenience! Could you please specify the full versions of AppCode ('About AppCode') and Xcode ('Preferences | Tools | Xcode') which you are using.
I am seeing the same thing. Running the app in the simulator seems to work (it stays connected and I see console output). Debugging does not stay connected. Usually it fails while the launch screen is showing. Running and debugging my app on my iPod fails.
Xcode 7.3 (7D175)
Same thing here
Build #OC-143.1824, built on February 9, 2016
JRE: 1.8.0_40-release-b119 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Version 7.3 (7D175)
(debugging works fine in XCode)
This seems similar to 207216225-AppCode-iOS-Simulator-not-starting-when-debugging, so I followed the instructions for enabling debug logging and emailed the file to support.
Is there an ETA for 3.4?
by the way, working like a charm with EAP
Cool, thanks for the info @Anna!
Yes, the EAP is working great for me, too. Thanks!
I know it is difficult to keep up on compatibility between AppCode and Xcode, but since it usually isn't an issue, I'm not in the habit of checking for issues before upgrading. It would be nice if information like this could be pushed to existing users (in-app announcement or email, perhaps). It would have saved me a morning's worth of downtime.
I agree, Jetbrains need to be a little more proactive in communicating these issues..
We are sincerely sorry for the inconvenience! Thanks for the suggestions, we will think about how to improve such important notifications.