Menu
I'm getting the following warnings/errors every time I run my ios emulator. At the moment the app is very simple, just a tutorial app. This is what I see in the console:
** BUILD SUCCEEDED **
Project successfully built.
Using /Users/wittner/Projects/nativescript/sample-Groceries/platforms/ios/build/emulator/sampleGroceries.app
Starting iOS Simulator
Apr 26 20:35:11 MacBook-Pro backboardd[5804]: SecTaskCopyDebugDescription: sampleGroceries[6014]
Apr 26 20:35:11 MacBook-Pro backboardd[5804]: SecTaskLoadEntitlements failed error=22 cs_flags=200, task->pid_self=-1
Apr 26 20:35:11 MacBook-Pro backboardd[5804]: SecTaskCopyDebugDescription: sampleGroceries[6014]
Apr 26 20:35:11 MacBook-Pro backboardd[5804]: SecTaskLoadEntitlements failed error=22 cs_flags=200, task->pid_self=-1
Apr 26 20:35:11 MacBook-Pro backboardd[5804]: SecTaskCopyDebugDescription: sampleGroceries[6014]
Apr 26 20:35:11 MacBook-Pro backboardd[5804]: SecTaskLoadEntitlements failed error=22 cs_flags=200, task->pid_self=-1
Apr 26 20:35:11 MacBook-Pro backboardd[5804]: SecTaskCopyDebugDescription: sampleGroceries[6014]
Apr 26 20:35:11 MacBook-Pro backboardd[5804]: SecTaskLoadEntitlements failed error=22 cs_flags=200, task->pid_self=-1
Apr 26 20:35:11 MacBook-Pro backboardd[5804]: SecTaskCopyDebugDescription: sampleGroceries[6014]
Apr 26 20:35:11 MacBook-Pro sampleGroceries[6014]: assertion failed: 15D21 13E230: libxpc.dylib + 71506 [6F98A9DA-B46E-3A2B-88D4-92F1EC77477F]: 0x7d
Apr 26 20:35:11 MacBook-Pro sampleGroceries[6014]: CONSOLE LOG file:///app/views/login/login.js:2:13: hello
the app is running fine and you can see my console.log() results at the end. I had some warnings during installation about cocoapods also but as I say, everything is, or seems to be running fine. Should I be worried?
728
An assertion failure occurs when the database server cannot continue normal processing and must shut down. You can correct some of the problems that cause assertion failures, such as disk issues.
In the running application program, the ASSERT statement recognized a. situation that should not have occurred. The runtime error was triggered for one of these reasons: - For the checkpoint group specified with the ASSERT statement, the. activation mode is set to "abort".
An assertion statement specifies a condition that you expect to be true at a point in your program. If that condition is not true, the assertion fails, execution of your program is interrupted, and the Assertion Failed dialog box appears.
The libxpc.dylib is a normal assertion. In fact it occurs with many of the different tool chains.
The Backboardd warnings are normal also on iOS.
61
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
