Search results for

“iPhone 16 pro”

80,724 results found

Post

Replies

Boosts

Views

Activity

**Apple Developer Program enrollment stuck for over a week — no response from support**
Hello, I've been trying to enroll in the Apple Developer Program for over a week now and I'm completely stuck. Despite multiple attempts and reaching out to Apple Support via both email and phone, I have received no resolution and no meaningful response. Here is a summary of my situation: I initiated enrollment and completed all required steps, including identity verification and payment. My enrollment was unexpectedly withdrawn without explanation. I attempted to re-enroll. The account remains in a pending/unresolved state with no approval or rejection. I have an app (already live on Google Play) ready for iOS submission that is being blocked by this issue. I have contacted Apple Support multiple times — via email and by phone — and have been advised to use the callback system at developer.apple.com/contact to reach the Membership & Enrollment team. Despite following this guidance, I still have no resolution after more than 7 days. Has anyone experienced a similar situation? Is there an
1
0
222
2w
Reply to Localized version of Application = Spam??
Thanks for the post, very interesting you went to an approached that will create a duplicate app instead of localization. I would actually focus on the reason you can’t localize in another language as that API has been proven to be great. I think we should focus on that. Apple’s automated systems and human reviewers are trained to flag apps that look and function similarly to existing apps. I believe the primary goal is to keep the App Store clean the preference is that a single app supports multiple languages and features, rather than having separate apps for different regions or languages. I think on the final result having 2 apps on the same region with different languages. If both apps are available in the same region that could be a really bad experience for the users. Let’s focus on the reason you can’t localize. Localization isn't just translating words; it's adapting the software. Developers extract all hard-coded text in the app and put them into a file called. The app then pulls the correct language
2w
Reply to Recurring FigXPCUtilities / FigCaptureSourceRemote err=-17281 logs when using AVCaptureVideoDataOutput on iOS 26.x
Similar issue here when starting an ARSession. iOS 26.3.1 on an iPhone 16 Pro. No issues running the same app on an iPhone 12 on iOS 18.6.2 `(Fig) signalled err=-12710 at <>:601 <<<< FigXPCUtilities >>>> signalled err=-17281 at <>:308 <<<< FigCaptureSourceRemote >>>> Fig assert: err == 0 at bail (FigCaptureSourceRemote.m:569) - (err=-17281)`
2w
Which Apple subscription offer best fits an in-app coupon-like flow?
Hello, I’m trying to understand which Apple subscription offer best fits a coupon-like flow in our app. Our ideal case is a 1-month Pro benefit that users can trigger inside the app: without entering a code manually possibly more than once over time then continue into a normal paid auto-renewable subscription Ideally, this would work for new, existing, and lapsed users, and if possible, even for users who are already actively subscribed (though that part is not required). From the docs, I understand that: Offer Codes require redemption Promotional Offers are for existing or previously subscribed users Introductory Offers are for new eligible users Win-Back Offers are for lapsed subscribers So my questions are: Is there any Apple-supported way to do this without manual code entry? Can the same user receive this kind of 1-month benefit multiple times over time? Which offer type is the closest fit? Is this use case partly incompatible with Apple’s subscription system? Thanks.
1
0
61
2w
Reply to XProtect makes app hang when running an AppleScript
[quote='880167022, parker9, /thread/810258?answerId=880167022#880167022, /profile/parker9'] GitHub has the actual source for that version in Releases [/quote] OK. I downloaded the app, the .dSYM, and the source code and took a look. First, the crash report has this: Binary Images: 0x102c6c000 - 0x102c9ffff DIM arm64 <3e247524da7930099f63cd12ace4ab0e> …/DIM I used dwarfdump to confirm that I have the right .dSYM: % dwarfdump --uuid DIM.app/Contents/MacOS/DIM UUID: 7A4DAC69-55A2-3D1B-B9E0-6A14AB2D5EEA (x86_64) DIM.app/Contents/MacOS/DIM UUID: 3E247524-DA79-3009-9F63-CD12ACE4AB0E (arm64) DIM.app/Contents/MacOS/DIM I then symbolicated those frames: % atos -l 0x102c6c000 -o DIM.app.dSYM 0x102c799bc 0x102c8b4d4 closure #1 in ViewController.restore(_:) (in DIM) (ViewController.swift:207) thunk for @escaping @callee_guaranteed () -> () (in DIM) + 28 Plugging that into the backtrace, I get this: Thread 1 Crashed:: Dispatch queue: com.apple.root.utility-qos 0 DIM … 0x102c6c000 + 55740 closure #1 in ViewControl
Topic: Privacy & Security SubTopic: General Tags:
2w
_MPRemoteCommandEventDispatch crashes on iOS 26.x devices.
I'm seeing crashes in _MPRemoteCommandEventDispatch on iOS 26.x devices in 3 apps. According to Bugsnag logs they are: NSInternalInconsistencyException: event dispatch <_MPRemoteCommandEventDispatch: sourceID=(null) ([HostedRoutingSessionDataSource] handleControlSendingCommand<2W5E>)> state:201> deallocated without calling continuation I attached a log from Xcode organizer matching Bugsnag crash. mpr_remote_command_event.crash When I set the brakpoint on the -[_MPRemoteCommandEventDispatch dealloc] I can see it it's hit every time I tap play or pause on locked screen play button. Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000002370420cc __pthread_kill + 8 (:-1) 1 libsystem_pthread.dylib 0x00000001e975c810 pthread_kill + 268 (pthread.c:1721) 2 libsystem_c.dylib 0x0000000198f8ff64 abort + 124 (abort.c:122) 3 libc++abi.dylib 0x000000018a7cf808 __abort_message + 132 (abort_message.cpp:66) 4 libc++abi.dylib 0x000000018a7be484 demangling_terminate_handler() + 304 (cxa_default_handlers.cpp:76) 5
4
0
933
2w
Reply to _MPRemoteCommandEventDispatch crashes on iOS 26.x devices.
The same problem on Xcode 26.3 NSInternalInconsistencyException event dispatch <_MPRemoteCommandEventDispatch: sourceID=SenderDevice = , SenderBundleIdentifier = , SenderPID = <9154> ((null))> state:201> deallocated without calling continuation userInfo: { NSAssertFile = _MPRemoteCommandEventDispatch.m; NSAssertLine = 39; } Crashed: Thread 0 CoreFoundation __exceptionPreprocess + 164 1 libobjc.A.dylib objc_exception_throw + 88 2 Foundation _userInfoForFileAndLine + 0 3 MediaPlayer -[_MPRemoteCommandEventDispatch dealloc] + 144 4 CoreFoundation -[__NSArrayI_Transfer dealloc] + 84 5 libobjc.A.dylib AutoreleasePoolPage::releaseUntil(objc_object**) + 204 6 libobjc.A.dylib objc_autoreleasePoolPop + 244 7 CoreFoundation _CFAutoreleasePoolPop + 32 8 CoreFoundation __CFRunLoopPerCalloutARPEnd + 48 9 CoreFoundation __CFRunLoopRun + 1976 10 CoreFoundation _CFRunLoopRunSpecificWithOptions + 532 11 GraphicsServices GSEventRunModal + 120 12 UIKitCore -[UIApplication _run] + 792 13 UIKitCore UIApplicationMa
Topic: Media Technologies SubTopic: Audio Tags:
2w
Biometrics prompt + private key access race condition on since iOS 26.1
We are using SecItemCopyMatching from LocalAuthentication to access the private key to sign a challenge in our native iOS app twice in a few seconds from user interactions. This was working as expected up until about a week ago where we started getting reports of it hanging on the biometrics screen (see screenshot below). From our investigation we've found the following: It impacts newer iPhones using iOS 26.1 and later. We have replicated on these devices: iPhone 17 Pro max iPhone 16 Pro iPhone 15 Pro max iPhone 15 Only reproducible if the app tries to access the private key twice in quick succession after granting access to face ID. Looks like a race condition between the biometrics permission prompt and Keychain private key access We were able to make it work by waiting 10 seconds between private key actions, but this is terrible UX. We tried adding adding retries over the span of 10 seconds which fixed it on some devices, but not all.
5
0
731
2w
ppq.apple.com returning 502 Bad Gateway - Unable to verify developer apps on device
Since this evening (March 10, 2026), I'm unable to launch any developer-signed app on my physical device (iPhone 16 Pro Max, iOS 26.4 beta 23E5223k). The error is: Unable to launch [app] because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user. On the device itself, it shows: Unable to Verify App - An internet connection is required to verify the trust of the developer. What I've tried: Created a new Apple Development certificate Deleted and reinstalled the app Restarted the device Tested on both Wi-Fi and cellular Confirmed Developer Mode is enabled Removed all third-party CA certificates from the device Verified the code signature is valid (codesign -dv shows correct Authority chain) The root cause: https://ppq.apple.com is currently returning 502 Bad Gateway. I confirmed this both from my Mac (curl -s -o /dev/null -w %{http_code} https://ppq.apple.com → 502) and from Safari on the device. This affects all developer-signed
141
0
12k
2w
Notarization Requests In Progress
Hello, I am following up on several notarization requests in order to understand the process better. I submitted my first notary request yesterday and it took several hours to complete (where I submitted two other requests along the way thinking they may be stuck). They were all accepted after ~3 hours had passed since the first request was made. In that time I discovered a bug and had to rebuild/codesign, and submitted to notarize again. I've now had two requests with the new build (.zip file) in progress for ~18 hours. The bug fix I made between builds was innocuous and I'm wondering if my jobs are getting flagged due to recent account lockouts when I was first setting up my organizations' developer account. I've seen several replies here in the forum from DTS Engineers - hi Quinn :), so I'm aware of the possibility of 'rare' in-depth analysis, however I've experienced it in 100% of my requests. What is causing my requests to always require in-depth analysis and is there anything I can do to prevent it? My
1
0
129
2w
Apple Silicon calling printf
What is the proper way to pass arguments to printf with multiple variables using ARM64 Apple Silicon? Example: fOutputStr: .asciz Element[%d] = %dn // formated output string for an output of: Element[4] = 9 This code (see below) works on Raspberry Pi 5, on my Mac Studio, I am getting this output, Element[9] = 1871655168 What do I need to do to use printf from an assembly language call with multiple variables? I am using the following code. ` .align 2 // memory alignment model for 64-bit ARMc #if defined(APPLE) .global _main // Provide program starting address to linker Mac OS _main: #else .global main // Raspian and Linux main: #endif // stack frame work setup START stp x29, x30, [sp, -16]! str x20, [sp, -16]! mov x29, sp // stack frame work setup END // setup printf call #if defined(APPLE) adrp x0, fOutputStr@PAGE add x0, x0, fOutputStr@PAGEOFF #else ldr x0, =fOutputStr #endif mov w1, #4 mov w2, #9 print_brk: #if defined(APPLE) stp X0, X1, [SP, #-16]! stp X2, X3, [SP, #-16
6
0
732
2w
Initial stack construction
I'm having problems constructing the initial stack for the guest executable for Valgrind on macOS 12 Intel. This seemed to work OK for macOS 11 but I'm getting a bad 'apple' pointer on macOS 12. The stack (constructed by Valgrind) looks like this higher address +-----------------+ <- clstack_end | | : string table : | | +-----------------+ | NULL | +-----------------+ | executable_path | (first arg to execve()) +-----------------+ | NULL | - - | envp | +-----------------+ | NULL | - - | argv | +-----------------+ | argc | +-----------------+ | mach_header * | (dynamic only) lower address +-----------------+ <- sp | undefined | : : The problem that I'm having is with the executable path (or the apple pointer). This points to NULL. The actual pointer to the executable=xxx string is 16 bytes lower in memory. The code for main starts with Dump of assembler code for function main: 0x0000000100003a90 <+0>: push %rbp 0x0000000100003a91 <+1>: mov %rsp,%rbp 0x0000000100003a94 <+4>: sub
5
0
241
2w
Reply to Bonjour Conformance Test WARNING in Multicast DNS SHARED REPLY TIMING resolution
Hi and thanks again for detailed response, First 10 was due to the information from Documentation/Conformance Test Outline.txt II.8 Shared Reply Timing The test tool issues a query for a shared (service PTR) record, and records how quickly the device answers. This test is repeated 10 times. So the assumption of this is understood and I agree to always have skewed binning. Attached below is a small test I threw together by pulling the response delay code out of mDNSResponder and then hard coding values Thank you for providing the code. I modify a bit to be able to build in our DUT // main.m // bonjour_ranTest // // Created by Kevin Elliott on 3/16/26. // #include #include #include #include // Added uint32_t mDNSPlatformRandomNumber(void) { return(arc4random()); } uint32_t mDNSRandom(uint32_t max) // Returns pseudo-random result from zero to max inclusive { #if 1 uint32_t ret = 0; uint32_t mask = 1; while (mask < max) mask = (mask << 1) | 1; do ret = mDNSPlatformRandomNumber() & mask;
2w
**Apple Developer Program enrollment stuck for over a week — no response from support**
Hello, I've been trying to enroll in the Apple Developer Program for over a week now and I'm completely stuck. Despite multiple attempts and reaching out to Apple Support via both email and phone, I have received no resolution and no meaningful response. Here is a summary of my situation: I initiated enrollment and completed all required steps, including identity verification and payment. My enrollment was unexpectedly withdrawn without explanation. I attempted to re-enroll. The account remains in a pending/unresolved state with no approval or rejection. I have an app (already live on Google Play) ready for iOS submission that is being blocked by this issue. I have contacted Apple Support multiple times — via email and by phone — and have been advised to use the callback system at developer.apple.com/contact to reach the Membership & Enrollment team. Despite following this guidance, I still have no resolution after more than 7 days. Has anyone experienced a similar situation? Is there an
Replies
1
Boosts
0
Views
222
Activity
2w
Reply to App Approved And Again Subscription - "Waiting For Review"
Hello - It appears that your app's two IAP subscriptions (the Pro Monthly and the Pro Annual) were approved by App Review on March 13, 2026 and should be live in your app at this time. Please let us know if you need anything else. Thank you.
Replies
Boosts
Views
Activity
2w
Reply to Localized version of Application = Spam??
Thanks for the post, very interesting you went to an approached that will create a duplicate app instead of localization. I would actually focus on the reason you can’t localize in another language as that API has been proven to be great. I think we should focus on that. Apple’s automated systems and human reviewers are trained to flag apps that look and function similarly to existing apps. I believe the primary goal is to keep the App Store clean the preference is that a single app supports multiple languages and features, rather than having separate apps for different regions or languages. I think on the final result having 2 apps on the same region with different languages. If both apps are available in the same region that could be a really bad experience for the users. Let’s focus on the reason you can’t localize. Localization isn't just translating words; it's adapting the software. Developers extract all hard-coded text in the app and put them into a file called. The app then pulls the correct language
Replies
Boosts
Views
Activity
2w
Reply to Recurring FigXPCUtilities / FigCaptureSourceRemote err=-17281 logs when using AVCaptureVideoDataOutput on iOS 26.x
Similar issue here when starting an ARSession. iOS 26.3.1 on an iPhone 16 Pro. No issues running the same app on an iPhone 12 on iOS 18.6.2 `(Fig) signalled err=-12710 at <>:601 <<<< FigXPCUtilities >>>> signalled err=-17281 at <>:308 <<<< FigCaptureSourceRemote >>>> Fig assert: err == 0 at bail (FigCaptureSourceRemote.m:569) - (err=-17281)`
Replies
Boosts
Views
Activity
2w
Which Apple subscription offer best fits an in-app coupon-like flow?
Hello, I’m trying to understand which Apple subscription offer best fits a coupon-like flow in our app. Our ideal case is a 1-month Pro benefit that users can trigger inside the app: without entering a code manually possibly more than once over time then continue into a normal paid auto-renewable subscription Ideally, this would work for new, existing, and lapsed users, and if possible, even for users who are already actively subscribed (though that part is not required). From the docs, I understand that: Offer Codes require redemption Promotional Offers are for existing or previously subscribed users Introductory Offers are for new eligible users Win-Back Offers are for lapsed subscribers So my questions are: Is there any Apple-supported way to do this without manual code entry? Can the same user receive this kind of 1-month benefit multiple times over time? Which offer type is the closest fit? Is this use case partly incompatible with Apple’s subscription system? Thanks.
Replies
1
Boosts
0
Views
61
Activity
2w
Reply to XProtect makes app hang when running an AppleScript
[quote='880167022, parker9, /thread/810258?answerId=880167022#880167022, /profile/parker9'] GitHub has the actual source for that version in Releases [/quote] OK. I downloaded the app, the .dSYM, and the source code and took a look. First, the crash report has this: Binary Images: 0x102c6c000 - 0x102c9ffff DIM arm64 <3e247524da7930099f63cd12ace4ab0e> …/DIM I used dwarfdump to confirm that I have the right .dSYM: % dwarfdump --uuid DIM.app/Contents/MacOS/DIM UUID: 7A4DAC69-55A2-3D1B-B9E0-6A14AB2D5EEA (x86_64) DIM.app/Contents/MacOS/DIM UUID: 3E247524-DA79-3009-9F63-CD12ACE4AB0E (arm64) DIM.app/Contents/MacOS/DIM I then symbolicated those frames: % atos -l 0x102c6c000 -o DIM.app.dSYM 0x102c799bc 0x102c8b4d4 closure #1 in ViewController.restore(_:) (in DIM) (ViewController.swift:207) thunk for @escaping @callee_guaranteed () -> () (in DIM) + 28 Plugging that into the backtrace, I get this: Thread 1 Crashed:: Dispatch queue: com.apple.root.utility-qos 0 DIM … 0x102c6c000 + 55740 closure #1 in ViewControl
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
2w
Reply to Unable to Download Apps via TestFlight - "The requested app is not available or doesn't exist" Error
Same issue for me. The latest build I can see on my phone is from my 1.0 build. I cannot see my most recent, which is the first one in 1.0.1
Replies
Boosts
Views
Activity
2w
_MPRemoteCommandEventDispatch crashes on iOS 26.x devices.
I'm seeing crashes in _MPRemoteCommandEventDispatch on iOS 26.x devices in 3 apps. According to Bugsnag logs they are: NSInternalInconsistencyException: event dispatch <_MPRemoteCommandEventDispatch: sourceID=(null) ([HostedRoutingSessionDataSource] handleControlSendingCommand<2W5E>)> state:201> deallocated without calling continuation I attached a log from Xcode organizer matching Bugsnag crash. mpr_remote_command_event.crash When I set the brakpoint on the -[_MPRemoteCommandEventDispatch dealloc] I can see it it's hit every time I tap play or pause on locked screen play button. Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000002370420cc __pthread_kill + 8 (:-1) 1 libsystem_pthread.dylib 0x00000001e975c810 pthread_kill + 268 (pthread.c:1721) 2 libsystem_c.dylib 0x0000000198f8ff64 abort + 124 (abort.c:122) 3 libc++abi.dylib 0x000000018a7cf808 __abort_message + 132 (abort_message.cpp:66) 4 libc++abi.dylib 0x000000018a7be484 demangling_terminate_handler() + 304 (cxa_default_handlers.cpp:76) 5
Replies
4
Boosts
0
Views
933
Activity
2w
Reply to _MPRemoteCommandEventDispatch crashes on iOS 26.x devices.
The same problem on Xcode 26.3 NSInternalInconsistencyException event dispatch <_MPRemoteCommandEventDispatch: sourceID=SenderDevice = , SenderBundleIdentifier = , SenderPID = <9154> ((null))> state:201> deallocated without calling continuation userInfo: { NSAssertFile = _MPRemoteCommandEventDispatch.m; NSAssertLine = 39; } Crashed: Thread 0 CoreFoundation __exceptionPreprocess + 164 1 libobjc.A.dylib objc_exception_throw + 88 2 Foundation _userInfoForFileAndLine + 0 3 MediaPlayer -[_MPRemoteCommandEventDispatch dealloc] + 144 4 CoreFoundation -[__NSArrayI_Transfer dealloc] + 84 5 libobjc.A.dylib AutoreleasePoolPage::releaseUntil(objc_object**) + 204 6 libobjc.A.dylib objc_autoreleasePoolPop + 244 7 CoreFoundation _CFAutoreleasePoolPop + 32 8 CoreFoundation __CFRunLoopPerCalloutARPEnd + 48 9 CoreFoundation __CFRunLoopRun + 1976 10 CoreFoundation _CFRunLoopRunSpecificWithOptions + 532 11 GraphicsServices GSEventRunModal + 120 12 UIKitCore -[UIApplication _run] + 792 13 UIKitCore UIApplicationMa
Topic: Media Technologies SubTopic: Audio Tags:
Replies
Boosts
Views
Activity
2w
Biometrics prompt + private key access race condition on since iOS 26.1
We are using SecItemCopyMatching from LocalAuthentication to access the private key to sign a challenge in our native iOS app twice in a few seconds from user interactions. This was working as expected up until about a week ago where we started getting reports of it hanging on the biometrics screen (see screenshot below). From our investigation we've found the following: It impacts newer iPhones using iOS 26.1 and later. We have replicated on these devices: iPhone 17 Pro max iPhone 16 Pro iPhone 15 Pro max iPhone 15 Only reproducible if the app tries to access the private key twice in quick succession after granting access to face ID. Looks like a race condition between the biometrics permission prompt and Keychain private key access We were able to make it work by waiting 10 seconds between private key actions, but this is terrible UX. We tried adding adding retries over the span of 10 seconds which fixed it on some devices, but not all.
Replies
5
Boosts
0
Views
731
Activity
2w
ppq.apple.com returning 502 Bad Gateway - Unable to verify developer apps on device
Since this evening (March 10, 2026), I'm unable to launch any developer-signed app on my physical device (iPhone 16 Pro Max, iOS 26.4 beta 23E5223k). The error is: Unable to launch [app] because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user. On the device itself, it shows: Unable to Verify App - An internet connection is required to verify the trust of the developer. What I've tried: Created a new Apple Development certificate Deleted and reinstalled the app Restarted the device Tested on both Wi-Fi and cellular Confirmed Developer Mode is enabled Removed all third-party CA certificates from the device Verified the code signature is valid (codesign -dv shows correct Authority chain) The root cause: https://ppq.apple.com is currently returning 502 Bad Gateway. I confirmed this both from my Mac (curl -s -o /dev/null -w %{http_code} https://ppq.apple.com → 502) and from Safari on the device. This affects all developer-signed
Replies
141
Boosts
0
Views
12k
Activity
2w
Notarization Requests In Progress
Hello, I am following up on several notarization requests in order to understand the process better. I submitted my first notary request yesterday and it took several hours to complete (where I submitted two other requests along the way thinking they may be stuck). They were all accepted after ~3 hours had passed since the first request was made. In that time I discovered a bug and had to rebuild/codesign, and submitted to notarize again. I've now had two requests with the new build (.zip file) in progress for ~18 hours. The bug fix I made between builds was innocuous and I'm wondering if my jobs are getting flagged due to recent account lockouts when I was first setting up my organizations' developer account. I've seen several replies here in the forum from DTS Engineers - hi Quinn :), so I'm aware of the possibility of 'rare' in-depth analysis, however I've experienced it in 100% of my requests. What is causing my requests to always require in-depth analysis and is there anything I can do to prevent it? My
Replies
1
Boosts
0
Views
129
Activity
2w
Apple Silicon calling printf
What is the proper way to pass arguments to printf with multiple variables using ARM64 Apple Silicon? Example: fOutputStr: .asciz Element[%d] = %dn // formated output string for an output of: Element[4] = 9 This code (see below) works on Raspberry Pi 5, on my Mac Studio, I am getting this output, Element[9] = 1871655168 What do I need to do to use printf from an assembly language call with multiple variables? I am using the following code. ` .align 2 // memory alignment model for 64-bit ARMc #if defined(APPLE) .global _main // Provide program starting address to linker Mac OS _main: #else .global main // Raspian and Linux main: #endif // stack frame work setup START stp x29, x30, [sp, -16]! str x20, [sp, -16]! mov x29, sp // stack frame work setup END // setup printf call #if defined(APPLE) adrp x0, fOutputStr@PAGE add x0, x0, fOutputStr@PAGEOFF #else ldr x0, =fOutputStr #endif mov w1, #4 mov w2, #9 print_brk: #if defined(APPLE) stp X0, X1, [SP, #-16]! stp X2, X3, [SP, #-16
Replies
6
Boosts
0
Views
732
Activity
2w
Initial stack construction
I'm having problems constructing the initial stack for the guest executable for Valgrind on macOS 12 Intel. This seemed to work OK for macOS 11 but I'm getting a bad 'apple' pointer on macOS 12. The stack (constructed by Valgrind) looks like this higher address +-----------------+ <- clstack_end | | : string table : | | +-----------------+ | NULL | +-----------------+ | executable_path | (first arg to execve()) +-----------------+ | NULL | - - | envp | +-----------------+ | NULL | - - | argv | +-----------------+ | argc | +-----------------+ | mach_header * | (dynamic only) lower address +-----------------+ <- sp | undefined | : : The problem that I'm having is with the executable path (or the apple pointer). This points to NULL. The actual pointer to the executable=xxx string is 16 bytes lower in memory. The code for main starts with Dump of assembler code for function main: 0x0000000100003a90 <+0>: push %rbp 0x0000000100003a91 <+1>: mov %rsp,%rbp 0x0000000100003a94 <+4>: sub
Replies
5
Boosts
0
Views
241
Activity
2w
Reply to Bonjour Conformance Test WARNING in Multicast DNS SHARED REPLY TIMING resolution
Hi and thanks again for detailed response, First 10 was due to the information from Documentation/Conformance Test Outline.txt II.8 Shared Reply Timing The test tool issues a query for a shared (service PTR) record, and records how quickly the device answers. This test is repeated 10 times. So the assumption of this is understood and I agree to always have skewed binning. Attached below is a small test I threw together by pulling the response delay code out of mDNSResponder and then hard coding values Thank you for providing the code. I modify a bit to be able to build in our DUT // main.m // bonjour_ranTest // // Created by Kevin Elliott on 3/16/26. // #include #include #include #include // Added uint32_t mDNSPlatformRandomNumber(void) { return(arc4random()); } uint32_t mDNSRandom(uint32_t max) // Returns pseudo-random result from zero to max inclusive { #if 1 uint32_t ret = 0; uint32_t mask = 1; while (mask < max) mask = (mask << 1) | 1; do ret = mDNSPlatformRandomNumber() & mask;
Replies
Boosts
Views
Activity
2w