Dive into the vast array of tools and services available to developers.

Posts under General subtopic

Post

Replies

Boosts

Views

Activity

Symbol not found from libc++ on iOS
Hi, I've had one user report that, when trying to dlopen() a dynamic library embedded inside a framework, they are hit by an error that a symbol from /usr/lib/libc++.1.dylib is not found. To the best of my knowledge, that's a single user being hit (let's say the event has a low probability). Here's the full error message from dlopen(): dlopen(clang.framework/clang, 0x0009): Symbol not found: ZNSt3122_libcppverbose_abortEPKcz Referenced from: <> /private/var/containers/Bundle/Application/<UUID>/a-Shell.app/Frameworks/clang.framework/clang Expected in: <UUID> /usr/lib/libc++.1.dylib How can I fix that? What could be the reason for libc++.1.dylib having a different content on a specific machine?
2
0
561
Aug ’24
Command [something] failed with a nonzero exit code
In most cases Xcode does a good job of surfacing build problems. If, for example, your Swift code has an error, Xcode’s Issues navigator shows you exactly what went wrong. However, that’s not universally true. In some cases the Issues navigator will show you a message like Command [something] failed with a nonzero exit code, where [something] is a build step like CodeSign or CompileC. To investigate these problems, look at the build report. The easiest option is to click on the issue in the Issues navigator. In most cases that will: Switch to the Reports navigator (View > Navigators > Reports). Select the correct build report on the left. Select the correct build step in the report editor. Expand its transcript (Editor > Expand Selected Transcripts). Note If that doesn’t work automatically, perform each of these steps by hand. That transcript includes both the details of the build step and all the information about the failure. For example, when I set my Other Code Signing Flags build setting to --varnish-waffles, I got the transcript included at the end of this post. As you can see, the codesign command really isn’t up for the task of varnishing waffles (-: Additionally, at the top of the report editor there’s an Export button. Click this to save a text file with the transcript of every build step. In DTS we call that the full build log. The full build log has a couple of nice properties: When investigating a complex build problem, use the full build log to trace build activity across multiple build steps. If you’re asking for help with a build problem, give your audience all the details by attaching the full build log. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" …/IssueNavigatorTest (in target 'IssueNavigatorTest' from project 'IssueNavigatorTest') cd /Users/quinn/Desktop/IssueNavigatorTest Signing Identity: "Apple Development: Quinn Quinn (7XFU7D52S4)" /usr/bin/codesign --force --sign 8CEF1273B13E1C6E7F6E73EBBEF42278F0D88C97 --varnish-waffles -o runtime --entitlements …/IssueNavigatorTest.xcent --timestamp\=none --generate-entitlement-der …/IssueNavigatorTest codesign: unrecognized option `--varnish-waffles' Usage: codesign -s identity [-fv*] [-o flags] [-r reqs] [-i ident] path ... # sign codesign -v [-v*] [-R=<req string>|-R <req file path>] path|[+]pid ... # verify codesign -d [options] path ... # display contents codesign -h pid ... # display hosting paths codesign --validate-constraint path ... # check the supplied constraint plist Command CodeSign failed with a nonzero exit code
0
0
777
Aug ’24
NO_CRASH_STACK
Yesterday 08/07/2024 we started to have a lot of NO_CRASH_STACK on our app released trough testflight, the release was created and released on the 07/30/2024 and is widely used by the beta testers. But for some reason this crash started to happen yesterday and we are not sure what the root cause is, we haven't made available any new builds under the same version or something, the only thing we did was to release a new version so the users can update from but it doesn't seem that the crash is happening on this new version only on the one from the 30th. Any idea what could be happening??
1
0
425
Aug ’24
rvictl not working on Mac OS Sonoma Version 15.0 Beta (24A5309e) with version 16.0 beta 4 (16A5211f)
This was working just yesterday 8/7, this morning a new Sonoma redwood tree screen saver appears (is it related? uncertain..) and now launching rvictl no longer starts. Running on a 16 GB Mac mini with M1. Yesterday I happily used Wireshark for debug development, today no longer. Moments ago I went through the process here to enable extensions (which was not required when I initially loaded Wireshark): https://support.apple.com/guide/mac-help/change-security-settings-startup-disk-a-mac-mchl768f7291/mac Following the process and enabling both checkboxes for user and remote management, I rebooted. Still unable to launch rvictl. One of Quinn's postings included below steps: sudo launchctl load -w /Library/Apple/System/Library/LaunchDaemons/com.apple.rpmuxd.plist sudo kextload /Library/Apple/System/Library/Extensions/RemoteVirtualInterface.kext In the process, a new driver was somehow auto-downloaded from Apple, and upon another requested reboot an "Allow" button appeared when looking at my Systems Settings->Privacy and Security. Reboot again, still no go. Another Quinn posting said only the first checkbox in the security settings was required. So I rebooted again, unselected the remote management checkbox. Reboot, and still no go. But now invoking rvictl hangs. There appear to be dozens of forum posts regarding rvictl, many laced with black magic voodoo suggestions to get it running. Eye of newt, toe of frog, wool of bat, and more. Security it seems becomes the bane of development. At this point, I'm uncertain what to try - though long for yesterday's debug bliss.
3
0
802
Aug ’24
IOS Beta 18.0 (22A5338b)
Updated my iPhone 14 Pro Max on 8/12/24 hoping to get rid off the problem connecting it to my vehicle's car play, it is a disaster on this matter. -Once it connects only makes a sound and does NOT even charged anymore. -Previously built connected via Bluetooth now this is null. -Battery drains faster. -Gets hotter. It is totally ridiculous we are guinea pigs on this. exposing our EXPENSIVE phones to their testing. This has nothing to do for developers other than utilizing us to ruin our phones on our expense. Luckily I have another brand phone and a second line NOT Apple and using it. Apple should be responsible if we are IN this testing be liable for any damage software might incurred do this. APPLE FIX THI NOW!!!!!
2
0
995
Aug ’24
Home Automation on Sensor and Time
Hi, I wanted to start the central heating if the temperature is below a certain level, I am home and the time is in a range. I created an automation but it didn't fire. I think it's because the sensor condition is "Temperature Drops Below" not "Temperature Is Below". In other words because the temperature was already below the level at the time the time window opened, the automation didn't fire. Does that sound correct? If so is it possible to do what I want which is to turn on the heating in the morning if it is cold?
0
0
455
Aug ’24
Streaming Mac Virtual Display
Is it possible to stream my Mac's virtual display to a website I create, so I can view my screen remotely? The main goal is to capture screenshots of my Mac's display using voice commands. The idea is to have the display streamed to the website, where I could say something like 'take a screenshot,' and the website would then capture and save a screenshot of the display. Has anyone done something similar or knows how this could be accomplished?
0
0
261
Aug ’24
App crashes on Real Device - Ok on Xcode and simulator
Hi there I recently uploaded a new version of my iPad App on Apple Store. It runs normal on Xcode and any simulator, it builds the Archive, it uploads to Apple Store, all normal. Nut users have reported that once they downloaded the new version, it crashes upon start up. At the moment I don't have a real device with me to test it out and check the crash logs. Some facts: (Maybe relevant) I only recently upgraded to OS Sonoma and Xcode 15 I (tried to) remove(d) everything, any reference concerning Firebase, because I was testing it out and gave up using it. So I don't know if this is relevant and if I removed everything I needed. Help
1
0
408
Aug ’24
XCTest stuck and has error when take snapshot element on screen has much elements
Dear Apple Developer [Background] We are developing a service running on test mode based on XCTest Framework to support streaming, remote and automation testing with iOS devices. After we upgrade macOS Sonama and Xcode 15 version for upgrade XCTest for support iOS 17 around Jan-2024, we saw We noticed that our running on test mode services stuck and hanging frequently after a period of time. We have investigate and tried debug code and we found that main thread stuck and hanging when it call requesting snapshot of accessibility hierarchy for app. At the same time, we noticed that the application we were testing stuck and hanging too. [Environment] Application testing: Tiktok MacOS: Sonoma 14.5 Xcode: Version 15.4 (15F31d) Device test: iPhone 12 (iOS 14.8.1) Log detail: t = 1524.15s Wait for com.ss.iphone.ugc.Ame to idle t = 1536.54s Find the Application 'com.ss.iphone.ugc.Ame' t = 1536.54s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 1597.56s Find the Application 'com.ss.iphone.ugc.Ame' (retry 1) t = 1597.56s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 1658.58s Find the Application 'com.ss.iphone.ugc.Ame' (retry 2) t = 1658.58s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 1718.58s Collecting extra data to assist test failure triage t = 1718.58s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 1778.59s Requesting snapshot of accessibility hierarchy for app with pid 509 2024-08-19 14:16:44.990260+0700 WebDriverAgentRunner-Runner[489:97809] Issue type: 0 2024-08-19 14:16:44.990428+0700 WebDriverAgentRunner-Runner[489:97809] Enqueue Failure: Failed to get matching snapshot: XCTPerformOnMainRunLoop work timed out after 60.0s ((null)) (null) 0 0 t = 1843.71s Find the Application 'com.ss.iphone.ugc.Ame' t = 1843.71s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 1874.72s Find the Application 'com.ss.iphone.ugc.Ame' (retry 1) t = 1874.72s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 1940.76s Find the Application 'com.ss.iphone.ugc.Ame' (retry 2) t = 1940.77s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 2005.80s Collecting extra data to assist test failure triage t = 2005.80s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 2066.58s Requesting snapshot of accessibility hierarchy for app with pid 509 2024-08-19 14:21:33.019582+0700 WebDriverAgentRunner-Runner[489:97809] Issue type: 0 2024-08-19 14:21:33.019687+0700 WebDriverAgentRunner-Runner[489:97809] Enqueue Failure: Failed to get matching snapshot: Unable to perform work on main run loop, process main thread busy for 30.0s ((null)) (null) 0 0 2024-08-19 14:21:33.020647+0700 WebDriverAgentRunner-Runner[489:97809] Issue type: 0 2024-08-19 14:21:33.020722+0700 WebDriverAgentRunner-Runner[489:97809] Enqueue Failure: No element snapshot found for Application 'com.ss.iphone.ugc.Ame'[0.00, 0.00] -> (200.0, 259.0) ((null)) (null) 0 0 2024-08-19 14:21:33.020801+0700 WebDriverAgentRunner-Runner[489:97809] *** Assertion failure in -[XCPointerEventPath initForTouchAtPoint:offset:], XCSynthesizedEventRecord.m:263 t = 2291.08s Find the Application 'com.ss.iphone.ugc.Ame' t = 2291.08s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 2352.10s Find the Application 'com.ss.iphone.ugc.Ame' (retry 1) t = 2352.10s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 2413.11s Find the Application 'com.ss.iphone.ugc.Ame' (retry 2) t = 2413.11s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 2473.12s Collecting extra data to assist test failure triage t = 2473.12s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 2533.13s Requesting snapshot of accessibility hierarchy for app with pid 509 2024-08-19 14:29:19.552744+0700 WebDriverAgentRunner-Runner[489:97809] Issue type: 0 2024-08-19 14:29:19.553054+0700 WebDriverAgentRunner-Runner[489:97809] Enqueue Failure: Failed to get matching snapshot: XCTPerformOnMainRunLoop work timed out after 60.0s ((null)) (null) 0 0 t = 2598.27s Find the Application 'com.ss.iphone.ugc.Ame' t = 2598.28s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 2659.29s Find the Application 'com.ss.iphone.ugc.Ame' (retry 1) t = 2659.29s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 2720.31s Find the Application 'com.ss.iphone.ugc.Ame' (retry 2) t = 2720.32s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 2780.33s Collecting extra data to assist test failure triage t = 2780.33s Requesting snapshot of accessibility hierarchy for app with pid 509 t = 2840.34s Requesting snapshot of accessibility hierarchy for app with pid 509 2024-08-19 14:34:26.806686+0700 WebDriverAgentRunner-Runner[489:97809] Issue type: 0 2024-08-19 14:34:26.806828+0700 WebDriverAgentRunner-Runner[489:97809] Enqueue Failure: Failed to get matching snapshot: XCTPerformOnMainRunLoop work timed out after 60.0s ((null)) (null) 0 0 2024-08-19 14:34:26.808114+0700 WebDriverAgentRunner-Runner[489:97809] Issue type: 0 2024-08-19 14:34:26.808205+0700 WebDriverAgentRunner-Runner[489:97809] Enqueue Failure: No element snapshot found for Application 'com.ss.iphone.ugc.Ame'[0.00, 0.00] -> (200.0, 259.0) ((null)) (null) 0 0 2024-08-19 14:34:26.809241+0700 WebDriverAgentRunner-Runner[489:97809] *** Assertion failure in -[XCPointerEventPath initForTouchAtPoint:offset:], XCSynthesizedEventRecord.m:263
1
0
779
Aug ’24