After I updated Xcode to 7.3 I am unable to start debugging with AppCode 3.3.2 & 3.3.3 I am just able to Run without debugging each time I start debbuging with appcode this happens in the console:
/Users/labib/Library/Caches/AppCode33/DerivedData/TestApp-e195af2c/Build/Products/Debug-iphonesimulator/TestApp.app
Stopping simulator session...
Simulator session started with process 3047
Process finished with exit code 0
JetBrains is aware of this issue and have a fix as part of the current RC (see their latest AppCode blog post).
Their current advice is essentially to download the RC version from their AppCode EAP page if you've already upgraded to XCode 7.3. NOTE: It does require a license or you can use a 30 day eval period.
Related
I'm running Xcode 14 beta 5 on macOS Ventura (13.0 Beta (22A5321d)) and when trying to run unit tests, not UI tests, plain old unit tests, I get this super annoying dialog when starting a test.
This is an SPM package, not an .xcodeproj.
If I click details, this is shown:
Details
Failed to prevent system sleep during UI testing. Error code: -536870211
Domain: IDEFoundationErrorDomain
Code: 1
User Info: {
DVTErrorCreationDateKey = "2022-08-17 20:06:42 +0000";
}
--
System Information
macOS Version 13.0 (Build 22A5321d)
Xcode 14.0 (21330) (Build 14A5294e)
Timestamp: 2022-08-17T22:06:42+02:00
Sometimes deleting derived data helps, sometimes not.
Any clues? I did not see this error in Xcode 14 beta 1 I think.
In terminal run: sudo pmset schedule cancelall
This fixed the issue for me on macOS Ventura Beta 5, Xcode 14 beta 6.
The answer came from this comment. It looks like a bug causes process powerd to issue too many assertions to pmset. This causes a problem when another process tries to create a PreventUserIdleSystemSleep assertion.
I am trying out Xamarin on the Mac. I have an oldish Mac that DID have Xcode 10.1 on it.
I tried to build the iOS app and got the following error:
Severity Code Description Project File Line Suppression State
Error The Xcode version installed on the Mac (10.1) is not compatible with this version of Visual Studio. This may cause unexpected warnings or errors when building and deploying iOS projects. Please install Xcode '11.3' or visit the documentation to learn more. 0
I upgraded the Mac to Caitlin and upgraded Xcode to 11.3.
I can connect to the Mac and actually can run the iPhone simulator with the app, however, if I run the build, I STILL get the same error, like its not figured out how to update itself?
I have done the 'forget this Mac' and even renamed it on the network in case there was some legacy in a file somewhere.
I have dumped the solution and created a new one from the templates and still get the same error ... hair being torn out...
It might be one of those things that just goes away after a while I don't know. Any ideas?
Thanks.
EDIT * I realised that I wasnt clear. I am running VS2019 on a PC connecting to my Mac.
Scenario:
I have updated to Qt 5.9.6 and I have Xcode 10.0 running on High Sierra.
I have a Qt App that builds for OSX and iOS. And it builds and runs all well with Qt 5.9.4.
Now, I want to update to 5.9.6 for a reason. When I try to build for iOS using Qt 5.9.6, I get the following error
Project ERROR: This mkspec requires Xcode 4.3 or later
Question:
Is there a way to get around this issue?
Note that the OSX build using Qt 5.9.6 just works fine. I have QMAKE_IOS_DEPLOYMENT_TARGET set to 10.0 for iOS case
PS:
I also deleted the .qmake.stash and the .pro.user file from the root directory and restarted QtCreator to try build from a a fresh start. But still get the same issue!
This is bug in Qt, use Qt 5.9.7 where this bug is fixed.
I created a basic gluon app for iOS and when I try to launch it (right-click on project > Tasks > launch > IPadSimulator) I get the output below. I have a macbook pro running Mac OS X Sierra, Xcode 8.3.3, Netbeans 8.2 with Gluon plugin 2.5.0.
Executing: gradle :launchIPadSimulator
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:createDefaultIOSLauncher
:compileIosJava UP-TO-DATE
:processIosResources UP-TO-DATE
:iosClasses UP-TO-DATE
:iosExtractNativeLibs UP-TO-DATE
:launchIPadSimulator
Root pattern javax.annotations.**.* matches no classes
Root pattern javax.inject.**.* matches no classes
warning: no debug symbols in executable (-arch i386)
2017-06-17 13:51:15.618 simlauncher[2058:23258] ERROR: dlopen(/Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/DTDeviceKitBase, 10): Library not loaded: #rpath/DVTDeviceFoundation.framework/Versions/A/DVTDeviceFoundation
Referenced from: /Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/DTDeviceKitBase
Reason: image not found
BUILD SUCCESSFUL
Total time: 15.489 secs
The build is successful, but the simulator does not start. I am able to launch the simulator and run apps from Xcode however.
I'm able to reproduce the issue, and it has already been reported elsewhere (here or here).
As you can see here, the current version of the jfxmobile plugin (1.3.5) is using on iOS MobiDevelop 2.3.0.
After Apple released iOS 10.3, several issues have been reported: deploying to mobile was failing after installation was complete (verification failed at 90%), and now the issue with the simulator.
MobiDevelop 2.3.1 has been recently released with some fixes.
Using this version I've just verified that the issue with the Simulator is fixed as well. Anyway, I've just created an internal issue to notify this problem.
When the jfxmobile plugin gets updated with the new MobiDevelop version, the issue will be solved.
In the meantime, if you need it, you can fork the repository, modify it and build it yourself.
I use Instruments 4.3 with UI automation tool for sometime successfully.
Recently I upgraded my target iPhone4 to iOS 5.1 and UI automation is now giving following error :"An error occurred while trying to run the script" for the moment a script is started, no further info than that.
Even when Instruments is running independently from Xcode the problem is still their, also when "run on record" is ticked but no script is selected.
I even reinstalled Xcode 4.3.1 but without success.
Runs fine on simulator and previous iOS version though.
If anyone encountered this issue and has a solution, please reply.
Thanks,