xcode github

Localizable.xcstrings is a string catalog, and so you are good. Do you localize the English column for your string catalog then? If not, Xcode will not generate the en.jproj for you. You can check with the following steps: Select Localizable.xcstrings in Xcode Project Navigator to show string catalog view. Select English to show the English localization. There, if the rows in the English(en) column are all grayed, Xcode won't generate the localization folder for you. So make sure you have at least one key localized. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Hello @wirmachenbunt , thank you for your question! Yes, this should be possible, but not through notifications. Notifications let you interact with your scene, but this API is only one-way. For reference, here is a forum answer from my colleague explaining how to use notifications to start a timeline notification. All timelines you configure inside Reality Composer Pro are actually animations like any other, and can also be accessed via an AnimationLibraryComponent. Note that the entity with the AnimationLibraryComponent with Timeline animations is going to be the root entity in your scene. Tip: If you're unsure which entity has this component, I recommend using print(myEntity) to print out a debug hierarchy to the console. Alternatively, you can use the Capture Entity Hierarchy tool in Xcode when debugging your application. Then, when you have your entity, you can start the animation like this: // Get the animation library from the entity. guard let animationLibraryComponent = myEntity.components[A

Do you check if the app bundle you submitted for App Store publication has the en.lproj folder? The value of the Languages field in the App Store is determined by the existence of .lproj folders in your app bundle. English is your default development language, and so Xcode should automatically generate en.lproj for you, if you use string catalogs for localization, but maybe you are not using a string catalog? Best, —— Ziqiao Chen  Worldwide Developer Relations.

Thanks for the post, love you selected emoji! This a great post for developers to provide their opinion on how they will handle that situation. In my modest opinion I would make sure the framework is build for external use and reference in the project as an external framework, if the code is part of the project, you can just include the file you want instead of using it as a framework. Otherwise just build the framework and use it as you would be using an external framework. Ensure that the framework search path includes the directory containing your framework bundle. You typically want to point to the or directory inside . Alternatively, use which automatically points to the correct build directory depending on the scheme (Debug/Release). If your framework is custom and part of the same project, ensure it's added to the Link Binary With Libraries phase of your app target. Consider copying the framework into the app bundle if needed by setting up a Copy Files build phase. If your framework and app are in sepa

I was not able to reproduce the failure you saw (training with BERT works with your toy data on my Mac, different OS/Xcode versions though). To clarify your macOS is Tahoe 26.1 and Xcode is 26.2, correct? Can you file a feedback with sysdiagnose? Meanwhile, I will try to get the exact same setup as yours to see if we can repro.

Thanks for the post, can you provide me a better screenshot on the target and device to run the target? Your screenshot looks like target to build against the simulator instead of the run target. Verify that the necessary simulator versions are listed and installed. If not, click the Install button next to the desired versions. What do you see on that screen? As a last resort, if none of the above solutions work, consider uninstalling and reinstalling Xcode. This can help resolve deep-seated installation issues. Albert Pascual
  Worldwide Developer Relations.

Thanks for your replies. I appreciate you... I received a news flash the other day. In my case, I have security software installed on my Mac that monitors and filters all network traffic. When Xcode tries to find iPhones or iPads on the same local network, it uses special local-network discovery traffic. That security software blocks or intercepts that traffic because it looks like unknown or unmanaged network activity. As a result, Xcode can’t see devices that are actually there. The devices weren’t the problem — the security software was. I had to temporarily stop it so Xcode could communicate directly with my local network. Crazy work man. So for those in a professional environment, temporarily close the security software and allow XCode to run its course. This worked for me.

Thank you for your compliment. Hope my boss is reading this :-) I am pleased that you have identified the issue. However, you have raised an important point. It appears that the error messages displayed on the website are not rendered in Xcode. I need to verify this information and would be grateful if Xcode could provide the same error message as the website. If you are willing to assist, I may request that you file an enhancement request to address this issue. Albert Pascual
  Worldwide Developer Relations.

Albert, You are a star, thank you. I had created another project six years ago and happened to use the same name, doh! I renamed the old one on GitHub and now all is good. I will amend the feedback that I had already created so as to detail the failure mode/unhandled condition. Hope you have a good day. Chris

Unfortunately, I still experience it on macOS 26.2 while running Xcode or simulator.

I have the same issue. launchd_sim could not bind to session on iOS 18.6 / 26.1 / 26.2 but when I downloaded 18.2 it worked fine. I tried clearing ~/Library/Developer/Xcode/DerivedData and /Library/Caches/com.apple.dt.Xcode but no success. I tried removing project build caches from System Settings -> Storage -> Storage Settings -> Developer, but no success. I deleted iOS Simulator 26.1 platform from Xcode > Settings > Components and then re-adding it but still no success.

Thanks for the clarification about Developer ID vs Apple Development and for the links. Per your advice, I’ve switched both the host app and the DNS Proxy system extension to Apple Development signing and the legacy dns-proxy entitlement. Current setup macOS: 15.7.3 (24G419) Xcode: 26.2 (17C52) Host app bundle ID: com.example.agent.MyMacProxy DNS Proxy system extension bundle ID: com.example.agent.MyMacProxy.dnsProxy System extension entitlements: com.apple.developer.networking.networkextension dns-proxy System extension Info.plist (built .systemextension inside the host app): NSExtension NSExtensionPointIdentifier com.apple.system_extension.network_extension NSExtensionPrincipalClass MyMacProxy.DNSProxyProvider There is no NetworkExtension key in this Info.plist (confirmed with plutil -p on the built .systemextension in both DerivedData and /Applications). The system extension is embedded at: MyMacProxy.app/Contents/Library/SystemExtensions/com.example.agent.MyMacProxy.dnsProxy.systemextension T