xcode github

@Ja239 my subscriptions and business agreements are all approved If the status of your subscriptions is Approved in App Store Connect, review their availability in App Store Connect. Confirm you select all the countries or regions where you want to sell the In-App Purchases. For more information, see TN3188: Troubleshooting In-App Purchases availability in the App Store. Yet, when the paywall in my app appears, and someone clicks the subscribe button to pay, the IAP isn't appearing. It just loads forever. For more information, see TN3188: Troubleshooting In-App Purchases availability in the App Store. When I tested in Xcode it just kept saying products not found. Id's are the same, bundle id is the same, ive done everything. If your app fails to display its products when testing In-App Purchases in Xcode or the Apple sandbox environment, see TN3185: Troubleshooting In-App Purchases availability in Xcode and TN3186: Troubleshooting In-App Purchases availability in the sandbox, respec

Is there an officially supported way for third-party iOS apps to access accelerometer data at sampling rates higher than ~100 Hz? So, my first question here is why you think you need a higher sampling rate? I ask because every developer who's asked this question has done so having gone through the same general development experience: They built an initial motion analysis engine which sort of worked, but had strange/inconsistent results and/or glitches. They increased the update interval and the situation improved marginally, but not completely. They continued increasing the update interval and saw improvements without actually resolving the issue until they hit the limit. Based on that experience, they've decided that the problem is caused by update frequency and if they can JUST get data a little bit faster everything will work fine. The problem here is that, in my experience, that entire analysis was built on the fundamentally false premise that the update frequency was actually the source of the problem. I

@barnabaskordas From Add your Icon Composer file to an Xcode project: If you create your Icon Composer file outside of Xcode, you can add it to your Xcode project anytime to view your icon in Simulator and on real devices. Just drag the Icon Composer file from Finder to the Project navigator, and Xcode provides feedback on where to drop it in a target folder. Alternatively, choose Add Files from the Add button at the bottom of the Project navigator and select your Icon Composer file in the dialog that appears. In the project editor, select the target and the General tab. Under App Icons and Launch Screen, ensure that the name in the App Icon text field matches the name of the Icon Composer file without the extension. You can have multiple Icon Composer files in your project but only one that matches the name in the App Icon text field. For an example, see the Configuring your app to use alternate app icons sample code.

Thanks for the post. I believe the issue you're encountering stems from attempting to install an iOS app build, even though it's marked as Designed for iPad, on a Mac. While Apple Silicon Macs can run iOS and iPadOS apps natively, there are nuances in TestFlight's handling of these builds that might cause installation issues if not configured correctly. I am not in the TestFlight team so I need to make sure this is the most accurate answer, I have invited the TestFlight team to post their answer in this thread however, they are not actively monitoring the forums. To make sure, ensure that the build settings in Xcode explicitly support macOS as a destination under Supported Destinations or via Universal Control settings for Apple Silicon. Open your Xcode project. Navigate to your target settings, and under the General tab, ensure that Deployment Info specifies iOS as the platform. For Universal apps, make sure Supported Destinations includes My Mac (Designed for iPad) if you specifically inte

Then Xcode shouldn't just add dupes of these certs. What happens is signing fails, Xcode gives no guidance. And so the Xcode UI has the option to add a new one. Then end up with dupe certs that cannot be cleaned out. Then the profiles fail if not the correct out of the 3 dupes, and signing still fails if the cert private key isn't in the keychain. Again no guidance from Xcode on any of these signing failures. Here's one error. Xcode shows Ineligible for the profile: Provisioning profile KramViewerProvision doesn't include signing certificate Developer ID Application: ... (hash...) Here's an error when the private key isn't in the Keychain. C6BA06....: no identity found Command CodeSign failed with a nonzero exit code

Thank you for the post. It appears that the issue is related to GitHub rather than Xcode. However, the error message could be more descriptive. Experiencing issues when trying to create a new remote GitHub repository from Xcode can be frustrating, especially when other functionalities are working fine. Can you go to the GitHub website and create the repository manually on their website? Ensure that your GitHub account has the appropriate permissions to create new repositories. You might want to try logging into GitHub via a web browser to verify your account status or as previously wrote, try to create the repo on their website and then just reference the link on Xcode. Manually Create on GitHub Website: Create the new repository directly through the GitHub website. Afterward, in Xcode, add this remote repository by going to or using the Terminal commands shown in advanced diagnostics to push your existing local

Welcome to the forums. So just select a simulator in Xcode for iPhone and iPad (e.g., iPhone 16 Plus 6.7 and iPad Air 13) and run the app on them. The screenshots generated by the simulator (cmd-S) will provide the right sized images. Note that you have to provide only one size for iPhone and one size for iPad.

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

OK. I don’t think you can optimise beyond that. Rather, I think you should use that as a baseline for performance work as you evolve your program. Speaking of that, An Apple Library Primer has links to various WWDC talks where the linker team discusses various topics. Most notably, the 2022 talk discusses launch times. It’s well worth a watch. Finally, just for context, the libSystem initialiser does a bunch of really critical stuff. For example, it has the code that sets up the App Sandbox, if the executable enables it. If you want to see this initialiser in action, open your true clone project, set a symbolic breakpoint on libSystem_initializer, and run it from Xcode. When you stop at the breakpoint, Xcode will show a page of disassembled code, but that’s not too hard to understand. And most of the symbols are present, so you can look up the source code in Darwin. IMPORTANT The Darwin open source isn’t guaranteed to match the source used to build the OS, but it’s usually close enough to be

Xcode is telling you that com.apple.developer.shazamkit isn’t a real entitlement. See Determining if an entitlement is real for more background on this. The solution is to do what Xcode suggested, that is, remove that property from your .entitlements file. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com