Xcode v13.4.1 libsystem_kernel.dylib`__abort_with_payload: - swift

I've a simple BLE test application which can NOT run inside Xcode. It says: "libsystem_kernel.dylib`__abort_with_payload:".
I can run it manually with the open Products/Release/HRM.app/Contents/MacOS/HRM but not with open Products/Release/HRM.app command...
I'm on the latest Monterey and Xcode. On an older machine with Mojave I can run it without this error message. What to check?

Related

Eclipse cant be opened on mac m1

I have installed eclipse aarch64 based on my mac m1.
it was working fine. later i stopped using it for few days but i was just opening and closing it just to make sure it is not crashing as it used to happen with x64 version.
Now even with aarch it is crashing.
As soon as i open it via launch pad it says 'The apllication 'Eclipse'can't be opened.
Here are the details of eclipse and jdk version that i am currently using.
Eclipse: eclipse-java-2021-12-R-macosx-cocoa-aarch64
Jdk: jdk-17_macos-aarch64_bin
I've just had the same problem on the second launch of Eclipse from a fresh installation. The solution was to re-sign the app with an ad-hoc signature:
sudo codesign --force --deep --sign - /Applications/Eclipse.app

Mac M1 chip machine, Mac OS BigSur Version 11.5.1 having problem with eclipse app. Its not opening after restarting machine

I Installed eclipse on my new mac m1 chip machine, It was working fine until I restart my machine. After restart the machine, the eclipse app is not opening also no error is shown in the display..
I am trying to open the app in terminal I am getting the following error
rosetta error: /var/db/oah/223263137464320_223263137464320/27e2cf6e452a44ee1a3ccc20e0409d562f65d18f27dd9ff3ebd552b78e52a4e3/eclipse.aot: attachment of code signature supplement failed: 3 Trace/BPT trap: 5
the solution giving in this is to upgrade the OS, but I already upgraded to the new OS version.
I can't find a solution anywhere, even in Apple forum sites
I faced a similar issue today. In my case, I'm using Anypoint Studio, which is built on top of Eclipse 4.19. After updating the OS, it worked again.

Got the "Error launching application on" after flutter run

I am flowing the official tutorial to install flutter and run the default app on my iPhone Device. After I execute the flutter run, the app is installed and launched on my iPhone but the logs show the bellow error. How do I solve it?
Launching lib/main.dart on My iPhone 6 in debug mode...
Automatically signing iOS for device deployment using specified development team
in Xcode project: XXXXXXXXXX
Running Xcode build...
└─Compiling, linking, and signing... 50.2s
Xcode builds done. 90.1s
Installing and launching... 41.1s
Error launching the application on My iPhone 6. <-- Error Here
It happens that there are some process needed to Flutter plugin correctly run on physical devices. I struggled with that and finally found that the processes idevicesyslog and iproxy were being silently blocked by MacOS.
You may have noticed already a message liked this:
or a similar one for idevicesyslog.
Once I went to System Preferences -> Security & Privacy in General tab and allowed this apps, everything works. Note that this screen shows only the last app that you tried to run. So I'd recommend that you run flutter app with preferences opened so you can (hopefully) see the messages appearing and click allow.
MacOS may warn you one more time about the file being downloaded from the internet. Just click open and you're good.
The error do not show again after reboot the iPhone.
Same error -- Running fine through Xcode, when I ran with flutter CLI, the app would open, but the terminal log output would crash with the error as in the post.
I ran flutter update and simultaneously turned iPhone off and back on. After doing that, the below popup appeared (on mac).
I believe after the install finished, I ran the below (which I ran several times before updating flutter and installing the popup):
flutter clean
rm -rf ios/Pods
flutter pub get
cd ios && pod install && cd ..
run the flutter app using flutter run from command line, then the MacBook will ask for permission to open the app and app runs,
(lldb) warning: libobjc.A.dylib is being read from process memory. This indicates that LLDB could not find the on-disk shared cache for this device. This will likely reduce debugging performance.
Error launching application on device-XXXXX.
Building & Replace with a newest version ios-deploy solved problems list aboved. Flutter SDK bundled a pre-built command ios-deploy in __PATH_TO_YOUR_Flutter_SDK_/bin/cache/artifacts/ios-deploy/, just replace it.
Please reference to: Flutter Error launching application on device issue .

"Unable to locate GDB" in Trigger Toolkit

I'm attempting to run an iPhone app in the Trigger Toolkit, but I keep getting "Unable to locate GDB" in the console, several seconds after "Connecting to remote debug server" . I've updated xcode, installed gdb separately through homebrew, and am able to run it (gdb) through the command line.
Thanks in advance for any relevant advice!
I'm guessing you're using a pre-v2.0.1 platform version here, and that you've updated to Xcode 5?
I was able to reproduce this error in that configuration. Xcode 5 doesn't support GDB, which we were previously using to communicate with the app running on your device.
If updating to use newer platform versions isn't an option for you, you could use an older installation of Xcode (you can have several versions installed as siblings), and use xcode-select to point us at it, e.g.:
sudo xcode-select --switch /Applications/Xcode4.6/Xcode.app

RCP Building for mac fails using Delta Pack

I am having troubles building my RCP Application for Mac using the Delta Pack. I have Delta Pack 3.7.2 installed and configured right (inserted into a target platform ) and the Building part completes just perfectly.
When I try to run the build app on my windows(Dev PC) it works fine. But when I zip the Mac version and try to run it on my mac, then it fails on every version I try:
Cocoa 32b,
Cocoa 64b,
Carbon etc
The app won't open and I don't get an error message.
Is there a way to get an error message anyway? Has anyone had this problem before?
When you build for a mac on a windows machine you should not build directly to a directory. Instead you should build to an archive. Then put this archive on the mac and expand it there. Then everything should work