what do you mean with executable markers? And can you give an example?
Post
Replies
Boosts
Views
Activity
I wanted to create an area light-source in RealityKit. This would be an option do so as RealityKit does not support area lights. Scenekit supports it, but did not get it operational and neither some other people looking at some posts on the internet.
when will Codebrain be available for developers?
Currently, others already supply it for different languages, e.g. Amazon - CodeWhisperer, .....
Anxious to see it also integrated in Xcode.
according https://developer.apple.com/documentation/visionos/bringing-your-arkit-app-to-visionos which states: “You can’t use Metal to create 3D content that integrates with the person’s surroundings. This restriction prevents apps from sampling pixels of the person’s surroundings, which might contain sensitive information.”
This will not be possible due to privacy reasons.
Maybe Apple developer people can react whether this will be possible in the future?
see reply
Same here. Tried a lot of things on the internet, e.g. clean install Xcode, install Xcode 16 beta 5, MacOS 15.1 Beta. Killed usbmux deamon etc. etc. All do not help.
phones: iOS 18.0 Dev beta (22A5326f), iOS 18.0 beta (22A5316k).
All not working.
I would expect more people have this issue, not limited to us only.
Checking with Apple support, but no feedback received yet, only send all diagnostics of phone and MacBook.
@Developer Tools Engineer
file it under Feedback Assistant, including indication that it is a duplicate of 131662031. Included the sysdiagnose for the MacBook, including various iPhones I have the issue with.
However, the workaround did not get me out of this state.
purchased an additional MacBook, installed Xcode etc. Not the beta versions. This one just works with the same phones on the beta iOS releases. So I am able to further debug, and hoping that non beta version of Xcode (in store) and macOS in the future will make my developer macBook working again correctly.
Note. It looks indeed something in CoreDevice, as finder can just connect to the phones normally.
@Developer Tools Engineer
The result of getting the details does not give a transportType back. below are the results.
I could not send whole part as Reply tool complains about language!
devicectl device info details --device 00008101-000219E40E28001E
Current device information:
• supportedDeviceFamilies: [1]
• thinningProductType: iPhone13,2
• udid: 00008101-000219E40E28001E
deviceProperties:
• ddiServicesAvailable: false
• developerModeStatus: enabled
• hasInternalOSBuild: false
• osBuildUpdate: 21G93
• osVersionNumber: 17.6.1
• rootFileSystemIsWritable: false
• bootedFromSnapshot: true
connectionProperties:
• authenticationType: manualPairing
• isMobileDeviceOnly: false
• lastConnectionDate: 2024-08-19 12:58:35 +0000
• pairingState: paired
• tunnelState: unavailable
• visibilityClass: default
@Developer Tools Engineer
Disabled Wifi on phone. It is showing (and accessible) all the time in Finder, but double checked in USB. There it is also visible.
With the same cables, it is also working with Xcode on another macBook Pro (running stable releases of macOS and Xcode).
The system diagnose was already reported in ticket: FB14875513.
In the meantime I also did a sysdiagnose with Coredevice profile enabled. These files I have also uploaded under the ticket. I hope you have access to those files.
Note: in the past did several things, like rebooting, reinstalling, restarting usbmux etc. etc. but all did not help.
@Developer Tools Engineer, some news? I do not get feedback in 'Feedback Assistant", so, I am still stuck. In the meantime I updated Xcode to Version 16.0 (16A242) the Release candidate, but does not help either. I do not expect that a fresh installation of Xcode from the store will help then either. So starting to get a little bit disappointed, as I do not want to reinstall macOS to an older version.
Since latest releases of xcode 16.0 Release candidate and macOS 15.1 Beta (24B5035e) I have access to the external devices again. Unclear how it is fixed, as I did not get any responses in the feedback assistant.