Good day, I'm trying to resolve the EU "Digital Services Act" compliance for my employer's Apple Developer account, but I'm stuck on verifying the phone number. The email verification code came through without any issue. We are located in South Africa, with a "+27" area code and the number I need to use here is a landline that comes through to the receptionist at our head office. This number does not have the ability to receive text messages, so I selected the "Didn't get a verification code?" link and chose the receive a phone call instead, however the call never comes through. Calling the number from my cellphone goes straight through to the receptionist, there are no digital switchboard prompts for the caller to select from. I tried this numerous times this Friday just past, and again twice now today, still no luck. I've requested an official document from my manager to see if I can go that route to verify the details, but so far nobody seems to be able to find an appropriate document for me to use... :( Is there anything else that I can do here?

Hello everyone!! I am writing to inquire about the procedures for testing an application I am developing for iOS devices. The application has been developed using Flutter, and I would like to make it available for testing on my colleague's iPhone, who serves as our QA tester. Currently, my account on the App Store is free, and I would like to ensure proper testing before proceeding with deployment to the Apple Store. As the application is quite large, I am unable to provide it in debug mode on the QA tester's device. Therefore, I would like to enable them to use the application on their personal device for a few days to provide comprehensive feedback on performance and features. Could you please provide guidance on how to proceed with this beta testing process? I am committed to adhering to all of Apple's guidelines and policies to ensure a high-quality user experience. I would be very grateful if anyone could help me out on this, Thank you.

I'm working on an Ionic iOS project and since I upgraded to macOS Sonoma 14.4.1 I get this error when I try to build my project in xcode 15.3. I tried cleaning the build folder executing pod deintegrate, pod clean and pod install upgrading cocoa pods with gem install cocoapods If I set User Script Sandboxing to No, the application builds, but I still get the error when I'm building the exact same commit/version on Ionic Appflow, which I have to do to publish the Application in the App Store. I'm using cocoapods 1.15.2

Hi! I need a little help here. I want to use my iPhone with Xcode, and I'm building an app that I want to preview on my device. The developer mode in Settings - Privacy and Security - Developer Mode won't enable. I click the switch to the green on, the device prompts me to restart, I restart it and then there is no last pop-up after the restart completes to confirm enabling. The option is also still off in Settings. I have done the process multiple times and still nothing. I have also tried manually enabling it from the Mac but also it fails with error 1. The full output from the Mac is: Request failed: An unknown error has occured 00008101-0005048E2251003A: Failed to enable Developer Mode (1) Does anyone know of a way to fix this or any recommendations? I have tried Reset all settings, fiddling with the WiFi, and adjusting Find My iPhone (although I don't think those have anything to do with Developer Mode). Any help is very appreciated.

After adding PrivacyInfo.xcprivacy following this Steps: https://vikramios.medium.com/itms-91053-missing-api-declaration-3c2bef935bd3 I am getting this error ❌ error: Multiple commands produce 'app_dir/PrivacyInfo.xcprivacy';

Hello, I have an Applescript application that launch a webserver that is compiled into it. This webserver is composed of httpd, php, openssl and curl among others. I'm using the --prefix parameter to compile everything where it needs to be. Until macOS 13, I had no problem with this setup. Since macOS 14, an error shows up in the Finder during the ./configure of curl : "cannot open the Application My.app as it may be damaged or incomplete" When this dialog alert appears, the ./configure script is suspended during : configure:25088: checking whether to enable IPv6 configure:25137: gcc -o conftest -Qunused-arguments -O2 -Wno-pointer-bool-conversion -Werror=partial-availability -I/Applications/MyApp.app/Contents/Resources/Webserver/zlib-1.3.1/include -L/Applications/MyApp.app/Contents/Frameworks -framework CoreFoundation -framework CoreServices -framework SystemConfiguration -L/Applications/MyApp.app/Contents/Resources/Webserver/zlib-1.3.1/lib conftest.c -lz >&5 configure:25137: $? = 0 configure:25137: ./conftest I tried the following with the conftest : otool -L conftest conftest: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 2420.0.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 1226.0.0) /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration (compatibility version 1.0.0, current version 1300.100.9) /Applications/MyApp.app/Contents/Resources/Webserver/zlib-1.3.1/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.3.1) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1345.100.2) The /Applications/MyApp.app/Contents/Resources/Webserver/zlib-1.3.1/lib/libz.1.dylib is present and signed for further Apple's notarization. ./conftest in another terminal window the error is different : Cannot open the application cause the developper cannot be verified. This error happens only when compiling inside a folder with an .app extension (which is assumed to be an application by macOS). If I use the --prefix toward a folder without the .app extension, everything works fine. Among every sources I compiled, curl is the only one causing me this. Nothing has changed in the curl's configure script for decades. I looked up to what could have changed from macOS 13 to 14 but I didn't find anything.

I'm building a Unity application for ios that also communicates with Firebase (and GDrive, if it makes a difference, as well as some other servers). When running it through Unity Build Automation with fastlane, this is what it's failing on. Help? inline-code[2024-04-10T09:53:11.680Z] - 7.4.1.2.7.4 - [0;36mINFO [0m: SwiftCompile normal arm64 Compiling\ AsyncAwait.swift,\ Result.swift,\ Storage.swift,\ StorageComponent.swift,\ StorageConstants.swift,\ StorageDeleteTask.swift,\ StorageDownloadTask.swift,\ StorageError.swift,\ StorageGetDownloadURLTask.swift,\ StorageGetMetadataTask.swift,\ StorageListResult.swift,\ StorageListTask.swift,\ StorageMetadata.swift,\ StorageObservableTask.swift,\ StoragePath.swift,\ StorageReference.swift,\ StorageTask.swift,\ StorageTaskSnapshot.swift,\ StorageTaskState.swift,\ StorageTokenAuthorizer.swift,\ StorageUpdateMetadataTask.swift,\ StorageUploadTask.swift,\ StorageUtils.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/AsyncAwait.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/Result.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/Storage.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/StorageComponent.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/StorageConstants.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/Internal/StorageDeleteTask.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/StorageDownloadTask.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/StorageError.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/Internal/StorageGetDownloadURLTask.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/Internal/StorageGetMetadataTask.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/F... [2024-04-10T09:53:11.680Z] - 7.4.1.2.7.4 - [0;36mINFO [0m: torageTokenAuthorizer.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/Internal/StorageUpdateMetadataTask.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/StorageUploadTask.swift /opt/workspace/workspace/arpalusdev.productrecognition.ios-provisioned-app/temp20240410-3408-1mgvzme/Pods/FirebaseStorage/FirebaseStorage/Sources/Internal/StorageUtils.swift (in target 'FirebaseStorage' from project 'Pods') [2024-04-10T09:53:11.680Z] - 7.4.1.2.7.4 - [0;36mINFO [0m: (2 failures)

I'm looking to build an app that can read the text of notifications (i.e the sender and body of whatsapp messages, sender and body of emails etc..) is this something possible within iOS?

I used the following command to sign a package, the output is as follows: productsign --sign "Developer ID Installer: Jie Tian (D29U75AWM7)" ~/Downloads/literate-enigma-1.0.pkg ~/Downloads/literate-enigma.signed.pkg productsign: using timestamp authority for signature Warning: unable to build chain to self-signed root for signer "Developer ID Installer: Jie Tian (D29U75AWM7)" productsign: signing product with identity "Developer ID Installer: Jie Tian (D29U75AWM7)" from keychain /Users/jeff/Library/Keychains/login.keychain-db productsign: Wrote signed product archive to ~/Downloads/literate-enigma.signed.pkg When I open the signed installer the following dialogue pops up:

Hi all I don’t even know if this is a help post or just a cry from my soul. I'll start from the very beginning. My firm is developing software for small and medium businesses. For us developers, there is nothing unusual about this. If the client's store, we transfer it beautifully and without problems to the mobile application. We have been releasing apps since 2019. And everything was fine, even excellent, until August 2022. In August, after submitting the application for review, I, as the account developer, received a notice that clause 3.2f was violated and that my account would be closed. It is clear that I immediately filed an appeal, but the Apple inspectors said that they would not change their minds. To say that I was shocked = to say nothing. Since then, I have filed 6 appeals, created other accounts (tried), so that our clients are calm that we are fulfilling our obligations. no response to appeals (no calls, no letters) Does anyone know how else to contact support? Because I have no more ideas, honestly - I'm broken. Thanks for reading, Tim

Hello, I have a script that I can run with launchd. I want it to be able to do some git operations. If I run my script manually (outside of launchd) things work great. If I run it within launchd, it seems to have issues with the sandboxing. git says: error Unable to read current working directory: Operation not permitted Here are the .plist and the .sh. Does anyone have any ideas what I can do? git seems to have many options about reading its configuration files; I assume that is what is going on here. Thanks! com.bolsinga.gitcmd.plist (substitute paths as appropriate): <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <!-- Copy this file to ~/Library/LaunchAgents cd ~/Library/LaunchAgents open Console.app and monitor syslog output. NOTE: in the following command, the plist extension is required. launchctl bootstrap gui/501 ~/Library/LaunchAgents/com.bolsinga.gitcmd.plist Look for related output in the syslog. Namely the executable this runs cannot be in ~/Documents, as it will get rejected. It works in ~/Applications launchctl list | grep bolsinga to see if it is running obviously, RunAtLoad below means it will run when loaded. launchctl bootout gui/501 ~/Library/LaunchAgents/com.bolsinga.gitcmd.plist to unload before re-loading when editing this file --> <plist version="1.0"> <dict> <key>Label</key> <string>com.bolsinga.gitcmd</string> <key>ProgramArguments</key> <array> <string>/Users/bolsinga/Applications/gitcmd.sh</string> <string>/Users/bolsinga/Documents/code/git/bin_utils/</string> </array> <key>RunAtLoad</key> <true/> <key>StandardErrorPath</key> <string>/tmp/com.bolsinga.gitcmd.err</string> <key>StandardOutPath</key> <string>/tmp/com.bolsinga.gitcmd.out</string> <key>WorkingDirectory</key> <string>/Users/bolsinga/</string> </dict> </plist> gitcmd.sh #/bin/sh # NOTE! This must be copied into ~/Applications. # So must any scripts it accesses! Otherwise it will not run from ~/bin/ DST_DIR="$1" if [ -z "$DST_DIR" ] ; then echo "No destination directory" 1>&2 exit 1 fi tgit() { GIT_TRACE2=true GIT_TRACE_SETUP=true git $* } echo PWD: `pwd` echo DST_DIR: $DST_DIR echo GIT `which git` tgit config --list tgit -C $DST_DIR config --list cd $DST_DIR tgit config --list

I have the XCode Version 15.3 (15E204a). When I try to compile my application, the following errors occur: Undefined symbol: _GDTCCTConstructiOSClientInfo Undefined symbol: _GDTCCTNetworkConnectionInfoNetworkMobileSubtype Linker command failed with exit code 1 (use -v to see invocation) Any solution to fix this issue?

We develop an SDK that is distributed as a statically linked, closed source Swift Package. Our customers have reported an issue when attempting to ship an application to the App Store using Xcode 15.3 that is preventing them from uploading the application: Asset validation failed Invalid Bundle. The bundle <AppName>.app/Frameworks/<Framework>.framework does not support the minimum OS Version specified in the Info.plist. (ID: 9cec9306-80a4-4503-a9bf-bd6e367f9679) Our SDK has a minimum deployment target of iOS 13.0 and the customer has a deployment target of 15.2. During local testing, I find that if my application and framework BOTH share the same deployment target of 13.0, then the App Store validation passes. If the application minimum version is greater than the framework minimum version, then the check fails. Researching on the internet, other people have suggested making the minimum deployment version of these Swift Packages to be GREATER than the app version. For instance, a handful of the Google SDKs shipped as binary packages on SPM are setting their minimum deployment version to 100.0 to work around this issue. I have tried this locally and found that if my app minimum deployment target is 15.2 and I set the MinimumOSVersion in the framework’s Info.plist file to 100, it passes the AppStore validation. It would appear that the check is inverted on App Store validation process. It is expected that an application can be submitted to the AppStore using a framework that works with older deployment targets. This issue appears to be related to the fact that Xcode 15.3 now embeds a .framework for statically linked framework dependencies. This is presumably done so that third party SDK's PrivacyInfo.xcprivacy can be included in the app package that it distributed to the app store. The binary portion of the statically linked library turns out to be much smaller (approx 35k) than the binary portion distributed in the .xcframework and appears to just be a small placeholder that does nothing since the actual code from the library is statically linked into the resulting application. The problem with the workaround that the other framework vendors have taken is that eventually (hopefully)  will fix this check and then these frameworks will appear to target a no existing iOS version. The other workaround that I spoke to our customer about was also extremely hackish and not really recommended was to resolve the Swift Package, then manually modify the contained Info.plist file to set the MinimumOSVersion in there to match what they are targeting for their application. This, however, then breaks the code signing of the SDK. So they then need to delete the _CodeResources folder from the resolved .xcframework. None of these work arounds are really sustainable and violate all the things right in the world. I have created feedback FB13704428 for this issue, but am hoping to raise further awareness as this is causing customers to not be able to ship applications using our, and many other, third party SDKs. Additional reading: https://github.com/google/GoogleSignIn-iOS/issues/375 https://github.com/google/abseil-cpp-binary/pull/6/files (If you examine the info.plist files in the two versions, you can see the minimum version set to 100 in the latest) https://github.com/AppsFlyerSDK/AppsFlyerFramework/issues/263 https://www.reddit.com/r/swift/comments/1bd7kxj/swift_ios_cannot_upload_to_testflight/

I'm tracking down a test error in openssl currently. Periodically we see a failure in a thread ******* test (as an example): https://github.com/openssl/openssl/actions/runs/8437420903/job/23198617572 In which the counter in this test reports going backwards, despite using atomic loads/stores to monotonically update it. we are unable to reproduce this issue on bare metal M1 hardware, its only on virtualized M1 hardware that we see this problem. One of the things that I have found is that an atomic load, when using apples distributed version of clang 15 is that the arm ldapr instruction is issued. however, if I manually implement the atomic load using an ldar instruction, the problem consistently abates. I believe (though I'm not yet certain) that github uses apples UTM virtualization on their CI runners. Is there an apple developer here that can comment on the behavior of the UTM virtual machine in regards to its handling of the ldapr instruction. It appears (though again, I'm not certain), that the virtualized M1 cpu may not be honoring (or not configuring) the localised ordering regions which the ldapr instruction honors, leading to incorrect sequential reads and writes.

We used to run this command to get wifi info on mac. /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I but it seems with latest 14.4.1 , airport command has been deprecated and advised to use wdutil. The problem with wdutil is that it only works with sudo. Is there a way we can still get all wifi metrics without sudo an mac?

我想知道对于5月1日之后，用户如果没有更新app，是否会受到影响？

{"duration_ms":"227124", "share_with_app_devs":0,"roots_installed":0,"bug_type ":"142", "os_version": "iPhone OS 17.3.1 (21D61)", "slice_uuid":"D479D5BB-1F9F-3405- BFAA-254435395FF3","is_first_party":0,"incident_id":"DFA88D80-8E48-46E9-8 A18-4BCOC496D6EB", "timestamp":"2024-02-14 14:18:15.00 -0500", "app_name":"backboardd", "name":"backboardd"} Date/Time: 2024-02-14 14:14:26.336 -0500 End time: 2024-02-14 14:18:13.460 -0500 OS Version: iPhone OS 17.3.1 (Build 21D61) Architecture: arm64e Report Version: 44 Incident Identifier: DFA88D80-8E48-46E9-8A18-4BC0C496D6EB Data Source: Microstackshots Shared Cache: B497C9DB-C62E-372D-B727-868EE7931E1 slid base address 0x186c3c000, slide 0x6c3c000 Shared Cache: E6753008-4C83-3F88-899E-202E9BAE2994 slid base address 0x19108000, slide 0x1108000 Command: backboardd Path: /usr/libexec/backboardd Resource Coalition ID: 73 On Behalf Of: 1 sample backboardd [66], 1 sample UNKNOWN [60] Architecture: arm64e Parent: UNKNOWN [1] PID: 66 Event: wakeups Action taken: none 45002 wakeups over the last 227 seconds (198 wakeups per second average), exceeding limit of 150 wakeups per second over 300 seconds Wakeups limit: 45000 Limit duration: 300s Wakeups caused: 45002 Wakeups duration: 227s Duration: 227.125 Duration Sampled: 226.25s Steps: 249 Hardware model: iPhone14,8 Active cpus: 6 HW page size: VM page size: 16384 16384 Advisory levels: Battery -&gt; 2, User -&gt; 3, ThermalPressure -&gt; 0, Combined - &gt; 2 Free disk space: 93.55 GB/119.07 GB, low space threshold 150 MB Vnodes Available: 62.95% (15107/24000, 12000 allocated, 12000 soft limit) Preferred User Language: en-US Country Code: US Keyboards: en_US QWERTY, emoji Emoji OS Cryptex File Extents: 1 Heaviest stack for the target process: 30 ??? (libsystem_pthread.dylib + 6660) [0x1f8b0ba04] 30 ??? (libsystem_pthread.dylib + 6500) [0x1f8b0b964] 29 ??? (libdispatch.dylib + 92280) [0x1969e4878] 29 ??? (libdispatch.dylib + 94212) [0x1969e5004] 17 ??? (libdispatch.dylib + 54952) [0x1969db6a8] 16 ??? (libdispatch.dylib + 50168) [0x1969da3f8] libsystem_pthread.dylib 0x1fb3be000 - 0x1fb3c1fff 10SurfaceAccelerator &lt;007AAAE6-5817-3A37-BDCC-0A650D29174E&gt; /System/Library/ PrivateFrameworks/lOSurfaceAccelerator.framework/lOSurfaceAccelerator 0x1c316000 - 0x1c339fff ANEServices &lt;8710EDDB-6F92-3D92-AB24-0D4C1BCB890D&gt; /System/Library/ PrivateFrameworks/ANEServices.framework/ANEServices 0x229c09000 - 0x229dc3fff H13ISP.mediacapture /System/Library/MediaCapture/ H13ISP.mediacapture 0х233403000 - 0x233776fff NRFV3 &lt;4A85805A- D53A-336D-B4A7-3E6DA86B6AA7&gt; /System/Library/VideoProcessors/ NRFV3.bundle/NRFV3 Powerstats for: appleh13camerad UUID: 5476D86A-AEE4-3CC1-B022-F853712B83C6 Path: /usr/sbin/appleh13camerad Shared Cache: B497C9DB-C62E-372D-B727-868EE7931E1 slid base address 0x186c3c000, slide 0x6c3c000 Resource Coalition ID: 187 Architecture: arm64e Start time: 2024-02-14 14:15:35.700 - 0500 End time: 2024-02-14 14:17:29.572 -0500 Num samples: 29 (12%) Primary state: 25 samples Non-Frontmost App, Non-Suppressed, User mode, Effective Thread QoS Unspecified, Requested Thread QoS Unspecified, Override Thread QoS Unspecified User Activity: O samples Idle, 29 samples Active Power Source: 29 samples on Battery, 0 samples on AC 29 ??? (libsystem_pthread.dylib + 6672) [0x1f8b0ba10] 29 ??? (libsystem_pthread.dylib + 9428) [0x1f8b0c4d4] 28 ??? (appleh13camerad + 199664) [0x104d90bf0] 28 ??? (CoreFoundation + 209244) [0x18ea0515c] 28 ??? (CoreFoundation + 209912) [0x18ea053f8] 24 ??? (CoreFoundation + 212384) [0x18ea05da0] 23 ??? (CoreFoundation + 214888) [0x18ea06768] 23 ??? (CoreFoundation + 220384) [0x18ea07ce0] 23 ??? (CoreFoundation + 220580) [0x18ea07da4] 22 ??? (10Kit + 48792) [0x197438e98] 18 ??? (appleh13camerad + 198828) [0x104d908ac] 17 ??? (appleh13camerad + 152568) [0x104d853f8] 17 ??? (appleh13camerad + 150332) [0x104d84b3c] 17 ??? (appleh13camerad + 89100) [0x104d75c0c] 11 ??? (appleh13camerad + 90160) [0x104d76030] 6 ??? (appleh13camerad + 114140) [0x104d7bddc] 3 ??? (appleh13camerad + 125900) [0x104d7ebcc] 2 ??? (appleh13camerad + 125504) [0x104d7ea40] 5 ??? (appleh13camerad + 126164) [0x104d7ecd4] ??? (appleh13camerad + 113792) [0x104d7bc80] 1 ??? (appleh13camerad + 126192) [0x104d7ecf0] ??? (appleh13camerad + 125900) [0x104d7ebcc] ??? (appleh13camerad + 125520) [0x104d7ea50] ??? (appleh13camerad + 125508) [0x104d7ea44] 3 ??? (appleh13camerad + 125504) [0x104d7ea40] ??? (appleh13camerad + 92848) [0x104d76ab0] 2 ??? (appleh13camerad + 131932) [0x104d8035c] 1 ??? (appleh13camerad + 131960) [0x104d80378] ??? (appleh13camerad + 99236) [0x104d783a4] ??? (appleh13camerad + 92648) [0x104d769e8] 1 ??? (appleh13camerad + 129768) (QuartzCore + 519284) [0x19005cc74] 4 ??? (QuartzCore + 486688) [0x190054d20] 3 ??? (QuartzCore + 487556) [0x190055084] 3 ??? (QuartzCore + 488956) [0x1900555fc] 3 ??? (10MobileFramebuffer + 11728) [0x1bf5d8ddO] 3 ??? (10Kit + 7056) [0x19742eb90] 3 ??? (10Kit + 6508) [0x1974296c] 3 ??? (libsystem_kernel.dylib + 4472) [0x1d6169178] 3 ??? (QuartzCore + 487292) [0x190054f7c] 1 ??? (10MobileFramebuffer + 11728) [0x1bf5d8dd0] 1 ??? (10Kit + 7056) [0x19742eb90] 1 ??? (10Kit + 6508) [0x19742e96c] 1 ??? (libsystem_kernel.dylib + 4472) [0x1d6169178] 1 4 ??? (QuartzCore + 524852) [0x19005e234] 2 ??? (QuartzCore + 603072) [0x1900713c0] 1 ??? (10MobileFramebuffer + 7660) [0x1bf5d7dec] 1 ??? (IOMobileFramebuffer + 7920) [0x1bf5d7ef0] ??? (IOMobileFramebuffer + 7596) [0x1bf5d7dac] 1 ??? (IOKit + 5692) [0x19742e63c] 1 ??? (IOKit + 5880) [0x19742e6f8] 1 ??? (IOKit + 6508) [0x19742e96c] 1 ??? (libsystem_kernel.dylib + 4472) [0x1d6169178] 1 1 ??? (QuartzCore + 600724) [0x190070a94] 1 ??? (QuartzCore + 605164) [0x190071bec] 1 ??? (Metal + 310724) [0x18e606dc4] 1 ??? (libdispatch.dylib + 80616) [0x1969e1ae8] 1 ??? (libdispatch.dylib + 17152) [0x1969d2300] 1 ??? (Metal + 30856) [0x18e5c2888] 1 ??? (Metal + 31384) [0x18e5c2a98] 1 ??? (10GPU + 19312) [0x20515db70] 1 ??? (10GPU + 19704) [0x20515dcf8] 1 ??? (10Kit + 208296) [0x19745fda8] 1 ‹Kernel mode&gt; 1 ??? (QuartzCore + 594540) [0x19006f26c] 1 ??? (IOMobileFramebuffer + 11016) [0x1bf5d8b08] 1 ??? (10Kit + 7056) [0x19742eb90] 1 ??? (10Kit + 6508) [0x19742e96c] ??? (libsystem_kernel.dylib + 4472) [0x1d6169178] 1 1 ??? (QuartzCore + 523680) [0x19005dda0] 1 ??? (QuartzCore + 302748) [0x190027e9c] 1 ??? (QuartzCore + 303720) [0x190028268] 1 ??? (QuartzCore + 807976) [0x1900a3428] 1 ??? (QuartzCore + 26328) [0x18ffe46d8] 1 ??? (QuartzCore + 24376) [0x18ffe3f38] 1 ??? (QuartzCore + 26328) [0x18ffe46d8] ??? (QuartzCore + 26328) [0x18ffe46d8] ??? (QuartzCore + 24376) [0x18ffe3f38] ??? (QuartzCore + 26328) [0x18ffe46d8] 1 ??? (QuartzCore

I'm a newbie to Reality Composer. Have constructed a couple of simple projects Have added text, and the "A a" is displayed, but as soon as it is selected for editing Properties, Xcode crashes. Running Ventura 13.3.1, and Reality Composer 1.5, Xcode 14.3.1. Will appreciate guidance on how to fix. Thanks!

Hi guys, I tried to build my app using EAS but got ✖ Failed to register bundle identifier com.fitlinez.pt Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later This request can not be processed right now - Service not available because of maintenance activities, please try again after some time. I've checked the System Status https://developer.apple.com/system-status/ and everything seems green! but the problem persists. Does anyone know how to fix it?

Hi Team, Is there a way we can get these metric without sudo Noise, MCS, TxRate after the deprecation of airport on latest mac?