As titled, I literally create a new project with UI Tests and it just fails.
/.../Test2/Test2UITests/Test2UITests.swift:37: error: -[Test2UITests.Test2UITests testLaunchPerformance] : Failed to terminate com.darylteo.Test2.Test2:27031: Failed to terminate com.darylteo.Test2.Test2:0
t = 60.29s Tear Down
Test Case '-[Test2UITests.Test2UITests testLaunchPerformance]' failed (60.288 seconds).
Test Suite 'Test2UITests' failed at 2022-09-18 13:34:26.714.
Executed 2 tests, with 1 failure (0 unexpected) in 65.396 (65.400) seconds
The app just goes black in simulator, but simulator is still interactive and the app can be hard stopped. I can't run a single test suite without it failing in this way, and running a single test repeatedly suffers from the same issue (works 1 time, fails the next)
I'm guessing this may be some kind of issue with the debugging connection to the simulator, but this kind of flakiness just completely makes XCUITest useless.
M1 MacBook Pro 16" with Pro Max
Monterey 12.5.1 (21GB3)
XCode Version 14.0 (14A309)
Simulator:
Version 14.0 (986.3)
SimulatorKit 624
CoreSimulator 857.7
Assistance appreciated 🙏
Other due diligence:
similar issue, but its 4 years old, and the error message is slightly different, reference to old xcode bug. UITest Failed to terminate com.test.abc:3708 after 60.0s; state is still `Running Foreground
similar issue, but only on Fastlane CI, not Simulator How to fix "Failed to terminate app" error in XCUItests?
another really old post that just brute forces the test. Will possibly try this as a workaround. XCTests failing to launch app in simulator intermittently
open Radar, 6 years old. No resolution http://www.openradar.appspot.com/25548393
Found the issue. I was running XCode in Rosetta mode due to another project that had dependencies that had not been compiled for m1.
Disable Rosetta and the problem no longer persists.
Hope this helps :)
Related
When I try to run my flutter-project code on the iOS simulator in VS code, I get the following error on the console:
Launching lib/main.dart on iPhone 11 Pro in debug mode...
lib/main.dart:1
Xcode build done. 24.4s
[VERBOSE-2:shell.cc(103)] Dart Error: Can't load Kernel binary: Invalid SDK hash.
[VERBOSE-2:dart_isolate.cc(171)] Could not prepare isolate.
[VERBOSE-2:runtime_controller.cc(415)] Could not create root isolate.
[VERBOSE-2:shell.cc(588)] Could not launch engine with configuration.
Thanks in advance.
Hi!
In my case, the error was caused by the forced shutdown of the IDE.
After manually selecting the libraries, I identified the one that was causing the problem, updated the project without it, and updated the project again with it.
With that the problem was solved.
Hope I have helped, if yes, please flag.
Could you delete the bin/cache folder, then run app
Open terminal and run: $ flutter channel beta
"it will install beta version, once installation is done, try it!"
"In case you willing to change the beta version to stable version you can use the following:"
$ flutter channel stable
Never had a lot of problems until the time to buy Macbook Air M1. Just yesterday my app was build without any error in Xcode 12.4. I did not make any special changes and today build failed:
/Users/userName/Projects/MyApp/ios/Pods/OpenSSL-Universal/ios/lib/libcrypto.a(cryptlib.o), building for iOS Simulator, but linking in object file built for iOS, file '/Users/userName/Projects/MyApp/ios/Pods/OpenSSL-Universal/ios/lib/libcrypto.a' for architecture arm64clang: error: linker command failed with exit code 1 (use -v to see invocation)
Please can you help me, how to solve it?
Looks like a missing Arm64 simulator slice in the OpenSSL-Universal CocoaPods distribution.
Make sure that you're using the latest version with pod update and contact the OpenSSL-Universal if there's still an issue.
I am getting an Error on the top of my interface builder in Xcode 10.3 and while clicking on report bug and checking the log.txt file I found out that fails to open simulator. However I am not starting any simulator.
Here is the Error found in Log.txt
Encountered an error communicating with IBAgent-iOS. (Failure reason: IBAgent-iOS failed to launch): Failed to boot device iPhone Xs (0B8270CC-2BFB-4BB6-90A5-6BA61468A1AD, iOS 12.4, Shutdown) for context <IBCocoaTouchToolLaunchContext: 0x7fe80e754ad0> toolName = IBAgent-iOS, description = <IBCocoaTouchPlatformToolDescription: 0x7fe80e2a0290> System content for IBCocoaTouchFramework-ElevenAndLater <IBSimulatorDeviceTypeDescription: 0x7fe80fab2f90> deviceType=com.apple.CoreSimulator.SimDeviceType.iPhone-XS (Failure reason: Failed to boot iPhone Xs (0B8270CC-2BFB-4BB6-90A5-6BA61468A1AD, iOS 12.4, Shutdown)): Unable to boot the Simulator. (Failure reason: launchd failed to respond.)
Error Domain=com.apple.InterfaceBuilder Code=-1 "Encountered an error communicating with IBAgent-iOS." UserInfo={NSLocalizedFailureReason=IBAgent-iOS failed to launch, NSUnderlyingError=0x7fe80ae44440 {Error Domain=NSPOSIXErrorDomain Code=60 "Operation timed out" UserInfo={NSLocalizedFailureReason=Failed to boot iPhone Xs (0B8270CC-2BFB-4BB6-90A5-6BA61468A1AD, iOS 12.4, Shutdown), NSLocalizedDescription=Failed to boot device iPhone Xs (0B8270CC-2BFB-4BB6-90A5-6BA61468A1AD, iOS 12.4, Shutdown) for context <IBCocoaTouchToolLaunchContext: 0x7fe80e754ad0> toolName = IBAgent-iOS, description = <IBCocoaTouchPlatformToolDescription: 0x7fe80e2a0290> System content for IBCocoaTouchFramework-ElevenAndLater <IBSimulatorDeviceTypeDescription: 0x7fe80fab2f90> deviceType=com.apple.CoreSimulator.SimDeviceType.iPhone-XS, NSUnderlyingError=0x7fe80bd300f0 {Error Domain=NSPOSIXErrorDomain Code=60 "Operation timed out" UserInfo={NSLocalizedFailureReason=launchd failed to respond., NSLocalizedDescription=Unable to boot the Simulator.}}}}, NSLocalizedRecoverySuggestion=Please check Console.app for crash reports for "IBAgent-iOS" for further information., NSLocalizedDescription=Encountered an error communicating with IBAgent-iOS.}
If anyone still looking for an answer to this after Xcode 13 update, I have tried everything they mentioned on the internet and nothing worked except one. The only thing that worked is the complete re-installation of Xcode. Completely uninstall/delete Xcode first and restart the mac and reinstall Xcode then all should be good.
Delete Xcode from Applications Folder and Empty Trash.
Go to ~/Library/Developer and Delete CoreSimulator, Xcode, XCTestDevices Folder. Empty trash
Goto ~/Library/Caches and delete everything starting with com.apple.dt.Xcode, Empty trash
Then Restart your Mac and reinstall Xcode. I used my downloaded Xcode app, AppStore installation will also work, I guess.
Now it all working.
Before that, I have changed the storyboard file using Open as Source Code mode (coz I couldn't open it in Interface Builder - Xcode just hang)
I changed the storyboard design device to iPhone 13 instead of the older device version it had.
<device id="retina6_7" orientation="portrait" appearance="light"/>
I change the existing line with this line. It kinda solve another issue of Xcode hanging, when trying to open with Interface Builder, but it didn't solve Encountered an error communicating with IBAgent-iOS issue when trying to install the app. That issue only got solved when I completely reinstalled the Xcode.
I have managed to fix it just by changing preview device on interface builder
In my case it helped:
clean project
remove derived data
close Xcode
restart Mac
I used DevCleaner XC helper app:
https://apps.apple.com/us/app/devcleaner-for-xcode/id1388020431?mt=12
removed everything, and after that restarted mac. No XC reinstall needed.
This problem caused because, I deleted all directories under "Library/Developer/Xcode" for a purpose. But, I realised I also deleted wrong directories in same time. Then I put back directories from the Bin. It is solved for me.
If you have or have had multiple versions of Xcode open, you may need to reboot or completely re-install the CoreSimulatorService, an evil, globally installed background service that somehow remains online and available to many versions of Xcode despite it being compatible with only one version.
See more here: https://stackoverflow.com/a/72946533/731285
Other symptoms of this issue: Simulators not showing up in the Window > Devices and Simulators listing and simctl throwing errors and being unable to find base iOS SDKs similar to the following:
$ xcrun simctl list
...
-- Unavailable: com.apple.CoreSimulator.SimRuntime.iOS-15-5 --
iPhone 8 (55A90310-8202-4A0D-968B-00F440D42210) (Shutdown) (unavailable, runtime profile not found)
See also:
Command CompileAssetCatalog failed with a nonzero exit code
Xcode device Unavailable, runtime profile not found
In my case, I just had to set team in
Project > Targets > Signing & Capabilities > Team > Personal Team
Device: iPhone 5 (Model A1429)
iOS version: 9.2 (13C75)
Titanium SDK: 4.0.0.GA
When I tried to run/distribute my app, I faced this error messages
[ERROR] : ** BUILD FAILED **
[ERROR] : The following build commands failed:
[ERROR] : Ld build/iVirtue.build/Debug-iphoneos/iVirtue.build/Objects-normal/arm64/iVirtue normal arm64
[ERROR] : (1 failure)
The warning in TiApp Editor > Deployment Targets said
iOS development requires [5.0, 9.0) but you have 9.2
Initially, when I haven't updated my Titanium Studio and my iOS version, the app was running perfectly. Please help.
I didn't clearly explain it before. The app i made was made on Titanium Studio, so installed the Appcelerator Studio and have the app exported. Now, it's working well. Thank you all, now i can close this matter.
Try to update the Titanium SDK to the latest 5.1.2.GA & all other components as well, because as you said that the app was working fine before so it is something related to the updates.
Use Titanium Studio to update everything available.
This seems to be a problem in your run configuration (or tiapp.xml). I suggest you first delete the run configuration, run the app again to define a new run configuration. Also check tiapp.xml to see if you have any references to iOS version?
You should also clean your project prior to running it after having deleted the run configuration :-)
/John
I try to Packaging project with Android Runtime For BlackBerry I done every thing
-Simulator, ADT- for eclipse .. when i test the app i got this error :
[2013-04-13 13:16:04 - BlackBerryTest] Packaging project BlackBerryTest
[2013-04-13 13:16:11 - BlackBerryTest] Launching BlackBerry Android Runtime...
[2013-04-13 13:16:20 - BlackBerryTest] Connecting to ADB...
[2013-04-13 13:17:23 - BlackBerryTest] Status ERROR: net.rim.ajde code=4 Connecting 192.168.72.128 to ADB failed! null children=[Status ERROR: net.rim.ajde code=0 Please check if the Android player was fully started when you got this error. If not, you can either increase the Android player launch timeout on the BlackBerry->BlackBerry Android Development Tools preference page or wait until the Android player is fully started and try again. null]
in the Simulator there is splash screen contain blackberry 10 logo start about 2 sec and then close and eclipse still Connecting to ADB... about a minute then I got error to connect.
**
UPDATE :
**
Now I got this message
04-25 12:01:15.539: I/navigatorshell(17789061): no app URI, just launch AP and exit
Any Idea ?
This is usually caused by the Android Runtime taking a very long time to load, and in some cases, never actually loading.
The root cause is that the simulator is running very slowly. If you haven't already, enable virtualisation in your BIOS, this makes a massive difference to simulator performance and solved this issue for me.
There's a video about this here: http://devblog.blackberry.com/2012/08/performance-increase-blackberry-10-simulator/