This is related to feedback submitted at https://feedbackassistant.apple.com.

OS: Sonoma 14.2.1 (23C71), I am porting a linux code (that uses C++, QT) to mac OS. after compiling the code on mac, I get segmentation error due to libGL.dylib. My question is how to avoid the segmentation error. debug messages when I run it using lldb: 2024-03-21 13:13:17.957964+0530 EdgeMarker[10094:150997] SecTaskCopyDebugDescription: EdgeMarker[10094]/0#-1 LF=0 2024-03-21 13:13:18.962117+0530 EdgeMarker[10094:150997] SecTaskLoadEntitlements failed error=22 cs_flags=20, pid=10094 2024-03-21 13:13:18.962246+0530 EdgeMarker[10094:150997] SecTaskCopyDebugDescription: EdgeMarker[10094]/0#-1 LF=0 Process 10094 stopped * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0xa80) frame #0: 0x00007ffa1c1295a4 libGL.dylib`glViewport + 22 libGL.dylib`glViewport: -> 0x7ffa1c1295a4 <+22>: movq 0xa80(%rax), %r9 0x7ffa1c1295ab <+29>: movq (%rax), %rdi 0x7ffa1c1295ae <+32>: popq %rbp 0x7ffa1c1295af <+33>: jmpq *%r9 Target 0: (EdgeMarker) stopped. Backtrace snippet: * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0xa80) * frame #0: 0x00007ffa1c1295a4 libGL.dylib`glViewport + 22 frame #1: 0x000000010000c427 EdgeMarker`MyGLCanvas::initializeGL(this=0x00007f8e4f857710) at MyGLCanvas.cpp:33:2 The error occurs when initializing an opengl window: void MyGLCanvas::initializeGL() { m_width = this->frameGeometry().width(); m_height = this->frameGeometry().height(); m_initialized = true; m_Eye[0] = 0.0f; m_Eye[1] = 0.0f; m_Eye[2] = -2.0f; //Actual code m_PerspectiveAngleDegrees = 45.0f; m_NearPlane = 0.01f; m_FarPlaneOffset = 100.0f; glViewport(0, 0, (GLint)m_width, (GLint)m_height); Before calling MyGLcanvas::initializeGL() there is a call to setFocus() function. SetFocus is a function used in GUI programming to give focus to a specific window or control within a window. My second question : Is setFocus valid is mac OS or is there an equivalent?

Hello, I'm in charge of the system at a certain company. We've been having trouble lately. Does anyone have the same problem? Our company have IN-HOUSE app for our employee. An issue has been occurring where the app can't be started after updating since last year. It is distributed to 2000 devices, and about 3 errors occur every time. When I try to start it I get the error below. "Unable to Verify App: An internet connection is required to verify the trust of the developer ... This app will not be available until verified." (IN JAPANESE：アプリを検証できません デベロッパー″iPhone　Distribution：...″の信用を確認するにはインターネット接続が必要です。確認が終わるまではこのアプリは使用できません。) *There were no problems with internet connectivity on any of the devices. *Provisioning profile has not expired. Moreover, Errors suddenly started to occur frequently even on devices that have not been updated since last month. The issue is occurring on the following devices. iOS16.6～17.3 iPhone 8, iPhone SE2 Although We restarted the iPhone and redistributed the app, the issue didn't improve. Currently, we are resolving by initializing the iPhone, but is there any workaround?

When a user uses a different developer account to log in to two applications back and forth, can the external identifier outerid be the same?

After reading An Apple Library Primer and watching Meet mergeable libraries (both really good resources) I'm sold on mergeable libraries. In my company we're working with static libraries as much as possible (both for precompiled dependencies and for our own Xcode projects). I can see that switching to mergeable libraries would (at least) improve iteration time because mergeable libraries would only be merged in release configs by default. You made it sound like it's "the holy grail of libraries". However, before starting the migration process I'd like to know: Is there any drawback to (merged) mergeable libraries when compared to using static libraries? I got the idea that mergeable libraries behave "almost" like static libraries after being linked "statically" with the app. What differences can I expect? Is there any situation where it's better to use static libraries instead of mergeable libraries? Thank you!

hello, I want to see the payload of a pkg file, after i expand it using pkgutil --expand-full file.pkg [path], i see it is converted into a directory. however, there are still two .pkg files in this directory. and again i use pkgutil --expand-full, this time it fails, the error is "Could not open product archive: ./Delinea.ConnectionManager.pkg" thanks

Learn techniques to help debug any coordinate space issue. View Technote TN3124 >

Hi team, we have an application for macOS, and previously, all binaries and installers were signed using one Apple account. However, we've transitioned to signing all binaries and installers with a different account. Note: Our application is not available on the App Store; we distribute it at an enterprise level to our customers. My question is: Can we expect app updates to function smoothly, or are there potential issues we should be aware of?

I am not able to remove the Activation Lock through MDM. I enabled the activation lock via https://mdmenrollment.apple.com/device/activationlock My device is listed in the ABM portal and i used the provided snippet here to generate the bypass code. I am getting the SUCCESS response of the above API and the activation lock also got enabled. But while removing the above activation lock via https://deviceservices-external.apple.com/deviceservicesworkers/escrowKeyUnlock and using the same escrow key that I used in the above api while activating the lock. I got the following error everytime <?xml version="1.0" encoding="UTF-8"?><ns:escrowKeyDeviceServicesResponse version="1" xmlns:ns="http://www.apple.com/cds/mdmescrowKeyDeviceServices/xml"><error code="1002" message="com.apple.cds.cyclops.mdm.MDMServiceException: Escrow key mismatch"/></ns:escrowKeyDeviceServicesResponse> Though this API of clearing the activation lock works perfectly fine when I enable the user-initiated activation lock, by enabling the Find My in the device. And use the bypass code as escrow_key that we receive from the device via device querry command.

Hi, I am trying to enroll in the Developer Program with my startup email account. However I keep getting the same message over and over: Your enrollment could not be completed. I have enabled 2 factor authentication Tried from the web Tried directly from the Apple Developer App (button shows disabled) Also, Phone Support is currently unavailable. Any help will be greatly appreciated.

I am building a unit test. The target of this unit test is my framework. My framework linked with couple of static libraries. When the test is running in simulator with host app it works fine. But when I try to test without host app I get following error from linker. PS: My test's xcconfig is similar to the host app's, and I can build the host app successfully. Undefined symbols for architecture arm64: "__mh_execute_header", referenced from: So what is __mh_execute_header and what framework/library it is defined in? Thanks for any help!

I am working on an sdk project and hope to find interface change information by comparing two doccarchive

Hi everyone, Our app runs on iOS deployment target 15.0. As per the WWDC 2022 session, page-in linking should be enabled for apps where chained-fixups is enabled. Since chained fixups are enabled from iOS deployment target 13.4+ which is true for our app, will page-in linking be applied to it? Is there some flag which we can use to confirm if it is applied for our app or not? We have tried using dyld_info tool but could not find a command which can provide this information.

panic(cpu 1 caller 0xfffffff017a8bf60): x86 CPU CATERR detected Debugger message: panic Memory ID: 0xff OS release type: User OS version: 21P3049 macOS version: 23D60 Kernel version: Darwin Kernel Version 23.3.0: Wed Dec 20 22:31:16 PST 2023; root:xnu-10002.81.5~10/RELEASE_ARM64_T8010 KernelCache UUID: 5055C553638BB2B9A72F9B074650402D Kernel UUID: 98C51133-18A2-37CC-8054-0C2A5A0CC992 Boot session UUID: 10AF6C85-ABD5-4EFC-B894-FCA5526A15B3 iBoot version: iBoot-10151.81.1 secure boot?: YES roots installed: 0 x86 EFI Boot State: 0xd x86 System State: 0x0 x86 Power State: 0x0 x86 Shutdown Cause: 0x5 x86 Previous Power Transitions: 0x10001000100 PCIeUp link state: 0x89473614 macOS kernel slide: 0xa400000 Paniclog version: 14 Kernel slide: 0x0000000011820000 Kernel text base: 0xfffffff018824000 mach_absolute_time: 0x11dabe93a329 Epoch Time: sec usec Boot : 0x65fa28af 0x00067d4f Sleep : 0x660be300 0x0005f658 Wake : 0x660be3c7 0x000e9358 Calendar: 0x660e9064 0x000acc96 Zone info: Zone map: 0xffffffddcf6fc000 - 0xffffffe3cf6fc000 . VM : 0xffffffddcf6fc000 - 0xffffffdeb5d60000 . RO : 0xffffffdeb5d60000 - 0xffffffdf02a2c000 . GEN0 : 0xffffffdf02a2c000 - 0xffffffdfe9090000 . GEN1 : 0xffffffdfe9090000 - 0xffffffe0cf6f4000 . GEN2 : 0xffffffe0cf6f4000 - 0xffffffe1b5d5c000 . GEN3 : 0xffffffe1b5d5c000 - 0xffffffe29c3c4000 . DATA : 0xffffffe29c3c4000 - 0xffffffe3cf6fc000 Metadata: 0xffffffe3d570c000 - 0xffffffe3d6f0c000 Bitmaps : 0xffffffe3d6f0c000 - 0xffffffe3d702c000 Extra : 0 - 0 TPIDRx_ELy = {1: 0xffffffdfe92a24e0 0: 0x0000000000000001 0ro: 0x0000000000000000 } CORE 0: PC=0xfffffff018a4f008, LR=0xfffffff018a4f008, FP=0xffffffeff4337ef0 CORE 1 is the one that panicked. Check the full backtrace for details. Compressor Info: 3% of compressed pages limit (OK) and 1% of segments limit (OK) with 0 swapfiles and OK swap space Panicked task 0xffffffe29c34b8c0: 0 pages, 227 threads: pid 0: kernel_task Panicked thread: 0xffffffdfe92a24e0, backtrace: 0xffffffeff437f6a0, tid: 406893 lr: 0xfffffff018a1ea90 fp: 0xffffffeff437f710 lr: 0xfffffff018b4d6f4 fp: 0xffffffeff437f780 lr: 0xfffffff018b4c728 fp: 0xffffffeff437f8a0 lr: 0xfffffff0189e1630 fp: 0xffffffeff437f8b0 lr: 0xfffffff018a1e4cc fp: 0xffffffeff437fc60 lr: 0xfffffff01909d030 fp: 0xffffffeff437fc80 lr: 0xfffffff017a8bf60 fp: 0xffffffeff437fcb0 lr: 0xfffffff017a72f40 fp: 0xffffffeff437fd10 lr: 0xfffffff017a79908 fp: 0xffffffeff437fd60 lr: 0xfffffff017a73978 fp: 0xffffffeff437fe00 lr: 0xfffffff017a727d0 fp: 0xffffffeff437fe30 lr: 0xfffffff018a74034 fp: 0xffffffeff437ff20 lr: 0xfffffff0189ec6c4 fp: 0x0000000000000000

Hello everyone, My iPhone has still not working for 3 months because of Error 1110. I hope the Apple software team can see this message and support us in fixing this issue soon, we lost our data and in this way, most people will not trust iPhones again if they can't find any fix even if this fix is by charge. Thank you. #1110 #error1110

Please bring back the a list of devices for devs to select from. This should not be hard to provide for your own products. Also, please allow users to set their own custom width/height dimensions. This is a really simple (arguably should be a mandatory for responsive design) feature.

Xcode 15.2 linker error (Assertion failed: (rebasePtr->target == low56), function writeChainEntry, file ChainedFixups.cpp, line 1218) The same project builds fine on Xcode 14.3.1. It also builds fine when building a debug build to device. Any ideas on what we might be doing wrong?

Hello Everyone, Please if you can assist me with the query I have regarding on how I can distribute my custom app to more than 100 iPads. I have a custom developed IOS App supplied by a vendor where I sign the app with my Apple Enterprise Certificate and Provisioning Profile and distribute to a group of iPads within my organization through a MDM. With the plan I am on with Apple Enterprise Program - it only allows me to register a maximum of 100 iPads. However I now need to distribute this app to around 200 iPads. Please assist with information on how I can increase my device count to more than 100. Thanks Kavitesh

https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-17_4-release-notes At the end of each release note there is a number, eg 121566625). What are these numbers?

My apple Account having Two active 'iOS Distribution' now Both are expected to Expire in next ~20 day's. Below are my queries looking for the details. a) can we create the new (third) iOS Distribution certificate for the build distribution ? b) how can we identified the current Active application provisioning profiles are boing with which iOS Distribution certificate (as under the Profile details showing two certificate having the same date) , so not able ti identified which certificate currently is in use?