Hi. I am using a Mac mini with M1. I created a symlink on the Desktop folder and set schg flag so that the system would not modify the link. Now I want to revert Desktop back to a normal folder, but the flag cannot be removed with this command: sudo chflags schg [path] Normally, booting in Single User Mode is advised for removing this specific flag since the system cannot alter anything when schg flag is set. But there is no longer Single User Mode in M1 Macs. I tried removing the flag in Recovery mode with the same command but it didn't help. What is the correct way to unset schg flag in M1 Macs? Thanks

I'm trying to debug my iOS app which designed only for iPhone on a M1 mac. But I got the error about signing. Xcode automatic signing failed with the note below: "Xcode failed to provision this target. Please file a bug report at https://feedbackXx and include the Update Signing report from the Report navigator." "Provisioning profile "iOS Team Provisioning Profile: com.XX" doesn't include the currently selected device "XX的MacBook Pro" (identifier XX)." How can I fixe it?

On an Apple Silicon M1 it is not possible to select the UIImagePicker controller to select an image. In the photo gallery, when you click on the image, the interface does nothing and does not react anything.To exit the interface you must click on the cancel button, but unfortunately it doesn't work also.It's working fine in real device device or intel processor mac simulator with same code and same iOS version. Currently I am testing on below configuration System OS: macOS Bigsur(11.2.2) chip: Apple M1 iOS Simulator: iPhone11(iOS 14.4) xCode:12.0.4 I get exception like below when i try to select image NSXPCConnection: 0x60000016a080 connection on anonymousListener or serviceListener from pid 17615: Warning: Exception caught during invocation of selector didSelectMediaWithInfoDictionary:, dropping incoming message and invalidating the connection. Exception: * -[NSURL URLByAppendingPathExtension:]: component, components, or pathExtension cannot be nil. -[NSURL URLByAppendingPathExtension:]: component, components, or pathExtension cannot be nil. ( 0 CoreFoundation 0x00007fff20421af6 __exceptionPreprocess + 242 1 libobjc.A.dylib 0x00007fff20177e78 objc_exception_throw + 48 2 Foundation 0x00007fff20860900 -[NSURL(NSURLPathUtilities) URLByDeletingPathExtension] + 0 3 PhotosUI 0x00007fff3faf656a -[PUPhotoPickerExtensionHostContext _UIImagePickerControllerInfoDictionaryFromPhotoPickerInfoDictionary:] + 2177 4 PhotosUI 0x00007fff3faf5b5b -[PUPhotoPickerExtensionHostContext didSelectMediaWithInfoDictionary:] + 34 5 Foundation 0x00007fff209290e3 __NSXPCCONNECTION_IS_CALLING_OUT_TO_EXPORTED_OBJECT_S1__ + 10 6 Foundation 0x00007fff20927e1b -[NSXPCConnection _decodeAndInvokeMessageWithEvent:flags:] + 2268 7 Foundation 0x00007fff20929412 message_handler + 206 8 libxpc.dylib 0x00007fff20055cac _xpc_connection_call_event_handler + 56 9 libxpc.dylib 0x00007fff2005603e _xpc_connection_mach_event + 905 10 libdispatch.dylib 0x000000010c73ba68 _dispatch_client_callout4 + 9 11 libdispatch.dylib 0x000000010c755ba8 _dispatch_mach_msg_invoke + 550 12 libdispatch.dylib 0x000000010c7420ad _dispatch_lane_serial_drain + 307 13 libdispatch.dylib 0x000000010c756a76 _dispatch_mach_invoke + 563 14 libdispatch.dylib 0x000000010c7420ad _dispatch_lane_serial_drain + 307 15 libdispatch.dylib 0x000000010c742f9d _dispatch_lane_invoke + 493 16 libdispatch.dylib 0x000000010c74ede2 _dispatch_workloop_worker_thread + 882 17 libsystem_pthread.dylib 0x00007fff61167499 _pthread_wqthread + 314 18 libsystem_pthread.dylib 0x00007fff61166467 start_wqthread + 15 ) Eager for this to be fixed out, it is really unbelievable issue. Kindly help me to solve this.

During the launch of M1, Apple mentioned clearly that new M1 has superior performance for running Tensorflow. On the ground, it's not working as expected and their fork has tons of issues and no continuous updates. On the other side, TensorFlow team said clearly that they are not required to attend to ARM64 support. I end in no support from both sides; Apple that is not caring to attend issues in their tensorflow fork & Google that they are not willing to support ARM64. Is there any advice for that?

I have an application that as part of it's functionality, reproduce music from the music library using the AVPlayerItem. it's working fine on iOS but on the Macbook with M1 processor the audio is not loading. Plist already contains the items: NSAppleMusicUsageDescription & NSAppTransportSecurity

Hi there. I'm using Unity to develop a WebGL application that has been working for years on Macs. With the new M1 Macs, though, I notice an issue where some of our 3d models flicker specifically on M1 Macs only. Updated Unity versions don't seem to fix anything, and editing the shaders doesn't seem to cause any change either. In the Unity Editor on this computer, everything renders just fine; it's only in an actual build that it's a problem. Has anyone seen an issue like this, either with Unity or with other WebGL? Does anyone have ideas on things I could try? Could this be a browser issue?

Hi, I think that a visual quality of hardware video encoder (VideoToolBox H.264) in M1 Macs is not great. I compared a software libx264 encoder (Mac) and NVIDIA Geforce (NVENC) on Windows 10 with the same bitrate or constant quality mode producing almost identical file size. I see many visual artefacts on a video encoded with VideoToolBox H.264 (1080p 60 fps) 3300K or CQ56. It's especially noticeable on video with animated photo slideshows and blur effect. Too many artefacts. NVENC and libx264 produce much better visual results with the same file size. I tested in my app and in Handbrake Beta for M1 which supports VideoToolBox H.264 encoding. Apple engineers can contact me for more details.

I'm now running Tensorflow models on my Macbook Air 2020 M1, but I can't find a way to monitor the Neural Engine 16 cores usage to fine tune my ML tasks. The Activity Monitor only reports CPU% and GPU% and I can't find any APIs available on Mach include files in the MacOSX 11.1 sdk or documentation available so I can slap something together from scratch in C. Could anyone point me in some direction as to get a hold of the API for Neural Engine usage. Any indicator I could grab would be a start. It looks like this has been omitted from all sdk documentation and general userland, I've only found a ledger_tag_neural_footprint attribute, which looks memory related, and that's it.

I have a MacBook Pro M1 (16 GB RAM), and testing CreateML's StyleTransfer model training. When I press «Train», it starts processing and fails with error «Could not create buffer with format BGRA -6662». During the «processing» it allocates about 4.5 GB of RAM. I guess it runs out of memory, however, I've closed all other programs and I can see that there's lot of free RAM when it fails. It happens even if I use just 3 small (500*500) images, 1 for each training, content and validation. So, how to fix it?

I can't paste anything into my simulator since switching to an M1 MacMini. I've tried ticking and unticking "automatically sync clipboard". I've also tried using the "send clipboard" option manually, but no success. I can seem to paste into safari on the simulator, but not any app I create in Xcode. I've tried multiple and even creating a new one fresh. I get the below snippet in the console complaining its unable to access some file. Looks like its an Xcode / M1 bug. I'm not running via rosetta. Does anyone know how to fix this, its become a real blocker for me testing my app 2021-06-11 12:00:28.656521+0100 camlKit-Example[3736:123707] [db] Failed to initialize client context with error Error Domain=NSOSStatusErrorDomain Code=-10817 "(null)" UserInfo={_LSFunction=_LSSchemaConfigureForStore, ExpectedSimulatorHash={length = 32, bytes = 0x15dde658 ed2a1267 ab2496d7 34f186ad ... ec431c65 02d68f35 }, _LSLine=409, WrongSimulatorHash={length = 32, bytes = 0xaf25dda9 e45baa35 610eaabd 5bc09901 ... 9cbe61f3 81d7b9d9 }} 2021-06-11 12:00:28.656878+0100 camlKit-Example[3736:123707] [db] _LSSchemaConfigureForStore failed with error Error Domain=NSOSStatusErrorDomain Code=-10817 "(null)" UserInfo={_LSFunction=_LSSchemaConfigureForStore, ExpectedSimulatorHash={length = 32, bytes = 0x15dde658 ed2a1267 ab2496d7 34f186ad ... ec431c65 02d68f35 }, _LSLine=409, WrongSimulatorHash={length = 32, bytes = 0xaf25dda9 e45baa35 610eaabd 5bc09901 ... 9cbe61f3 81d7b9d9 }} 2021-06-11 12:00:28.656957+0100 camlKit-Example[3736:123707] [db] Failed to initialize client context with error Error Domain=NSOSStatusErrorDomain Code=-10817 "(null)" UserInfo={_LSFunction=_LSSchemaConfigureForStore, ExpectedSimulatorHash={length = 32, bytes = 0x15dde658 ed2a1267 ab2496d7 34f186ad ... ec431c65 02d68f35 }, _LSLine=409, WrongSimulatorHash={length = 32, bytes = 0xaf25dda9 e45baa35 610eaabd 5bc09901 ... 9cbe61f3 81d7b9d9 }} 2021-06-11 12:00:28.657397+0100 camlKit-Example[3736:123707] [claims] Upload preparation for claim 1B09A1C9-1B93-4AB0-B91D-F8789C91AB3C completed with error: Error Domain=NSCocoaErrorDomain Code=256 "The file “fb19cda6511c09d17006da7aefa63f10ea73f68b” couldn’t be opened." UserInfo={NSURL=file:///Users/simonmcloughlin/Library/Developer/CoreSimulator/Devices/CD0E07DE-8C9C-4466-978B-1F6E635EE0E2/data/Library/Caches/com.apple.Pasteboard/eb77e5f8f043896faf63b5041f0fbd121db984dd/fb19cda6511c09d17006da7aefa63f10ea73f68b, NSFilePath=/Users/simonmcloughlin/Library/Developer/CoreSimulator/Devices/CD0E07DE-8C9C-4466-978B-1F6E635EE0E2/data/Library/Caches/com.apple.Pasteboard/eb77e5f8f043896faf63b5041f0fbd121db984dd/fb19cda6511c09d17006da7aefa63f10ea73f68b, NSUnderlyingError=0x600002813ae0 {Error Domain=NSOSStatusErrorDomain Code=-10817 "(null)"}}

My iOS-app shows a map and may be the user's location. At some point it will request the "always" location permission. On iOS all is well. The app also runs pretty neat on M1 macs so far, except for the part where it wants to request that permission. I also think it never asked me for the "Permission when in use" on the M1. However, after the user granted the always-permission on iOS, he'll be shown the screen of the GPS tracker. Since recording GPS tracks doesn't make much sense on M1, I'd like to show the user that screen, but disable the start button. So how do I test for M1? P.S. I'd not ask such a dumb question, if I didn't get this error: (including these strange quotes) „POI Toolbox“ kann nicht installiert werden Domain: IDEInstallLocalMacService Code: 1 Failure Reason: Versuche es später noch einmal. Recovery Suggestion: Failed to finalize LSBundleWrapper mutator instance for {...BUNDLE_ID...} -- System Information macOS Version 11.4 (Build 20F71) Xcode 12.5.1 (18212) (Build 12E507) Timestamp: 2021-06-28T12:31:13+02:00 The "failure reason" doesn't say anything helpful. It means "Try again later."

We tried installing ipa file in m1 Mac ( tried both mac11 and mac12 silicon mac), but it failed with error informing - Error Domain=ASDErrorDomain Code=660 "Could not create PKProduct". Attaching the log and plist details ipa-failure-devicelog.txt the plist - install application command

(environment: macOS 11.4, Xcode 12.4, iOS simulator 14.4) The below test does not passed when a project's architectures for "Any iOS Simulator SDK" contains X86_64 only. (Open a new project with architectures arm64 passes) import UniformTypeIdentifiers class UTTypeTests: XCTestCase {     func testThatItConvertsFromMIMEType() {         if #available(iOS 14.0, *) {             guard let mp4Type = UTType(mimeType: "video/mp4") else {                 return XCTFail("Could not decode from MIME type.")             }                          XCTAssertEqual(mp4Type, UTType.mpeg4Movie)         } else {         }   } } similar issue happens on deprecated method UTTypeCopyPreferredTagWithClass

Hi. I'm trying to catch leaks in my C program and I get an error Failed to gain authorization in the Leaks tool on Macbook Pro 13 M1 2020. Xcode 12.5.1 Likewise, when I run leaks in the terminal, I get a warning Process is not debuggable I am using the gcc with -g to compile my C code. Earlier, on Macbook Pro 13 Intel 2014, I have successfully used the tool for similar tasks. Is this possible on the M1?

firebase_core: Using Firebase SDK version '8.3.0' defined in 'firebase_core' Downloading dependencies Installing Firebase (8.3.0) Installing FirebaseCore (8.3.0) Installing FirebaseCoreDiagnostics (8.4.0) Installing Flutter (1.0.0) Installing GoogleDataTransport (9.1.0) Installing GoogleUtilities (7.5.0) Installing PromisesObjC (2.0.0) Installing firebase_core (1.4.0) Installing hexcolor (0.0.1) Installing nanopb (2.30908.0) Generating Pods project Integrating client project Pod installation complete! There are 3 dependencies from the Podfile and 10 total pods installed. [!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target Runner to Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig or include the Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig in your build configuration (Flutter/Release.xcconfig). Failed to build iOS app Error output from Xcode build: ↳ objc[37638]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libauthinstall.dylib (0x1f2887ad8) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1115102b8). One of the two will be used. Which one is undefined. objc[37638]: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x1f2887b28) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x111510308). One of the two will be used. Which one is undefined. 2021-08-02 21:40:05.452 xcodebuild[37638:437148] CFURLRequestSetHTTPCookieStorageAcceptPolicy_block_invoke: no longer implemented and should not be called ** BUILD FAILED ** Xcode's output: ↳ note: Using new build system note: Building targets in parallel note: Planning build note: Analyzing workspace note: Constructing build description note: Build preparation complete /Users/saizayarhtet/Desktop/ideaProduct/lottery_ace/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.5.99. (in target 'Flutter' from project 'Pods') error: Failed to create provisioning profile. There are no devices registered in your account on the developer website. Plug in and select a device to have Xcode register it. (in target 'Runner' from project 'Runner') error: No profiles for 'com.LA.lotteryAce.lotteryAce' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'com.LA.lotteryAce.lotteryAce'. (in target 'Runner' from project 'Runner') Encountered error while building for device.

Is Apple planning to fix the M1-Pytorch incompatibility? I've tried to build from source but I thought the M1 was supposed to be better with machine learning software.

I am much busy working on my Xcode project for a sticker pack. My sticker pack has passed running on my iPhone. However, I cannot see where my app icon is. I have checked out my iMessage. I can see there is my app icon on the keyboard. It is working. I am confused. Why not on the Home Screen?

Hello, Please help me solve this error: IB Designables: Failed to render and update auto layout status for ViewController (BYZ-38-t0r): dlopen(Demo.app, 1): no suitable image found. Did find: Demo.app: mach-o, but not built for platform iOS-sim I create new simple application. Then I create custom view with IB Designables and this broke Storyboard. I have a lot of projects in which I use Storyboard and now I cannot edit them. Thanks. Xcode: 12.5.1 (12E507) MacOS: 11.5.1 (20G80) Chip: Apple M1

We are seeing mysterious crashes in our app when running on the Apple Silicon machines using Rosetta. The crash is coming from Apple's runtime and dyld libraries, and always has the same kind of stack, but without much useful information. All have the same pattern of 5 stack frames, the bottom being dyld, and then 4 in runtime, but all just addresses, no idea what symbols are being called Sometimes the offset values are the same, other times they are not. When you group them together, we have at least two sets of stacks; but close enough that it appears the same root issue. Only these two libraries appear to be loaded, so perhaps it's a crash on launch before things are adequately setup, or something weird happens during the crash and we are only getting a small part of the picture captured in the .crash, or some corruption happens All are in Apple Silicon machines Some are on macOS 11, and some on macOS 12, so it's not a Monterey beta issue They are all crashing for reason Code Signature Invalid, but this seems unreliable, if indeed we can launch the app afterwards without issue, which appears to be the case (based on log reports we've received). Here is a typical example (with some app info redacted): Version: ??? Code Type: X86-64 (Translated) Parent Process: ??? [1] User ID: 503 Date/Time: 2021-08-06 14:38:06.408 +0200 OS Version: macOS 11.5.1 (20G80) Report Version: 12 Time Awake Since Boot: 21000 seconds Time Since Wake: 15000 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (Code Signature Invalid) Exception Codes: 0x0000000000000032, 0x0000000106675000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace CODESIGNING, Code 0x2 kernel messages: VM Regions Near 0x106675000: VM_ALLOCATE (reserved) 106671000-106675000 [ 16K] r--/r-- SM=NUL reserved VM address space (unallocated) --> mapped file 106675000-107ff9000 [ 25.5M] r-x/rwx SM=COW Object_id=695dd8f1 mapped file 107ff9000-107ffd000 [ 16K] r-x/r-x SM=COW Object_id=6aaf57f1 Thread 0 Crashed: 0 runtime 0x00007ffdffe9ac40 0x7ffdffe96000 + 19520 1 runtime 0x00007ffdffea3df4 0x7ffdffe96000 + 56820 2 runtime 0x00007ffdffea35ec 0x7ffdffe96000 + 54764 3 runtime 0x00007ffdffe9a440 0x7ffdffe96000 + 17472 4 dyld 0x000000020683f000 0x20683f000 + 0 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000106675000 x1: 0x000000030d81b730 x2: 0x0000000000000218 x3: 0x0000000000000012 x4: 0x0000000000000004 x5: 0x0000000001984000 x6: 0x0000000000000000 x7: 0x0000000000000a40 x8: 0x0000000000000007 x9: 0x0000000000000012 x10: 0x0000000106675fff x11: 0x0000000100000000 x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x000007d900018601 x16: 0x00000000000000c5 x17: 0x000000000220bef3 x18: 0x000000030d81b073 x19: 0x000000030d81b730 x20: 0x000000030d81aa78 x21: 0x0000000106675000 x22: 0x0000000000000004 x23: 0x0000000106675000 x24: 0x0000000000000003 x25: 0x0000000000000001 x26: 0x000000030d81ab90 x27: 0x000000020683f000 x28: 0x000000030d823960 fp: 0x000000030d81aa20 lr: 0x00007ffdffea267c sp: 0x000000030d81a9b0 pc: 0x00007ffdffe9ac40 cpsr: 0x20000000 far: 0x0000000106675000 esr: 0x92000006 Binary Images: 0x20683f000 - 0x2068dafff dyld (852.2) <57DB2053-BFD5-3683-97C6-F1DB2A1F1D09> /usr/lib/dyld 0x7ffdffe96000 - 0x7ffdffec5fff runtime (203.58) <52A2E5D0-FAA3-34EF-8BB7-07F73718C034> /usr/libexec/rosetta/runtime External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 0 thread_create: 0 thread_set_state: 0 VM Region Summary: ReadOnly portion of Libraries: Total=1048K resident=0K(0%) swapped_out_or_unallocated=1048K(100%) Writable regions: Total=19.8M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=19.8M(100%) VIRTUAL REGION REGION TYPE SIZE COUNT (non-coalesced) =========== ======= ======= STACK GUARD 56.0M 1 Stack 8176K 1 VM_ALLOCATE 10.5M 1 VM_ALLOCATE (reserved) 1132K 3 reserved VM address space (unallocated) __DATA 288K 4 __DATA_CONST 32K 1 __LINKEDIT 272K 4 __TEXT 816K 2 mapped file 4.8G 11 =========== ======= ======= TOTAL 4.9G 28 TOTAL, minus reserved VM space 4.9G 28 Any help or guidance is much appreciated. I cannot say for sure this is an Apple issue, as I have no way to reproduce it reliably, either in our app or another. But it seems doubtful it's a bug in our app. Thank you!