“xcode github”

Hi there, New to this forum. I have an iOS/iPadOS app already published in the App Store, and it works great as a Mac Catalyst app on my Mac. However when uploading to App Store Connect, I get the message: Failed Registering Bundle Identifier The app identifier maccatalyst.nl.lai.prep-app cannot be registered to your development team because it is not available. Change your bundle identifier to a unique string to try again. So the organizer adds the maccatalyst in front of the Bundle Identifier automatically, but for some reason I get the message it's not available. I've already added the macOS App as a platform on App Store Connect. The Bundle ID (nl.lai.prep-app) is obviously registered as the app is already available on iOS/iPadOS and I have enabled 'Mac Catalyst' in my App id Configuration on the developer portal. In Xcode macOS (Mac Catalyst) has been added as a destination. I contacted developer support, but they couldn't see anything wrong 🤷‍♂️ and suggested I would ask the developer communit

Hello, I have a question regarding Apple's policy on third-party SDK signatures. I have reviewed the official documentation here: https://developer.apple.com/support/third-party-SDK-requirements/ Our app is developed in the following environment: Minimum Target: iOS 15 Xcode: 26.2 Engine: Unreal Engine 4.27.2 We are integrating the Firebase SDK into our project. However, we are experiencing app crashes caused by an issue within the GoogleAdsOnDeviceConversion.xcframework included in the Firebase SDK (related to a memory optimization issue in UE4). According to an official response from the Firebase team, this crash can be resolved by wrapping the Firebase SDK in a dynamic XCFramework. We have confirmed that this solution does indeed fix the crash. The problem is that wrapping the Firebase SDK in a custom dynamic XCFramework removes all of the original Firebase SDK signatures. The documentation on third-party SDK signatures, which I referenced earlier, states that a signature is required for the Fireb

Hello, I made my app icon with Icon Composer and added the .icon file directly to my Xcode project. I noticed that the icon preview in Icon Composer looks one way, while the icon shown on the App Store looks different. Details: I am using the .icon file directly in the project I am not using an exported PNG for the app icon I did not add a separate background image The background was set with fill in Icon Composer The preview in Icon Composer looks as expected The App Store version has a different appearance I would like to ask whether this difference may come from: App Store processing caching or a recommended Icon Composer setup for background fill If anyone has seen something similar, I would appreciate any guidance. I can also share screenshots of the Icon Composer preview and the App Store result.

Hello, I created my app icon with Icon Composer and use the .icon file directly in my Xcode project. The preview in Icon Composer looks as expected, but the icon on the App Store has a different appearance. For reference: .icon file is used directly no separate background image was added background was set with fill in Icon Composer the difference appears on the App Store side Has anyone seen this before? I’m trying to understand whether this is related to App Store processing, caching, or Icon Composer background setup. I’ve attached: Any guidance would be appreciated.

com.apple.WebKit.WebContent process is being killed by the kernel’s memorystatus jetsam mechanism when it exceeds the ActiveHard 2048 MB limit, even though the iPhone has 12 GB physical RAM and hundreds of thousands of free pages available. This causes the exact same WebProcess → GPUProcess crash that was reported in thread 822200, but now the root cause is clearly visible in the kernel log. The crash only occurs on iPhones, never on iPads (even older ones). Environment Failing devices: iPhone 17 Pro (12 GB RAM) x 2 — iOS 26.3, 26.4, 26.4.1 Working devices (same page, same iOS): iPad Pro 2018 — iOS 26.1 (stable) iPad Pro 2025 — iOS 26.4 (completely stable) Reproduces in Safari and in WKWebView (Capacitor/Ionic app) Actual Logs (kernel + WebKit) `logApr 15 21:23:33 iPhone kernel[0] : memorystatus: com.apple.WebKit.WebContent [1596] exceeded mem limit: ActiveHard 2048 MB (fatal) Apr 15 21:23:33 iPhone kernel[0] : memorystatus: killing process 1596 [com.apple.WebKit.WebContent] in high band FOREGROUND (

Overview When using SwiftUI Map with .standard(elevation: .realistic) and a globe-style presentation, the map unexpectedly renders as a flat 2D map instead of a 3D globe / realistic terrain view. In the same view, switching to .hybrid(elevation: .realistic) preserves the expected 3D globe behavior. This appears to be a rendering bug or regression specific to the .standard style under globe mode, not an app-level issue. The issue is reproducible in my app’s competition map screen and has also been reported by other developers online. Steps to Reproduce Create a SwiftUI Map. Bind it to a MapCameraPosition. Apply a standard map style with realistic elevation: .mapStyle(.standard(elevation: .realistic)) Configure the UI so the user can switch between: standard + globe hybrid + globe Zoom out / interact with the map in globe mode. Expected Results Map with .standard(elevation: .realistic) should continue to render with globe / 3D realistic terrain behavior, consistent with realistic elevation support and similar t

I am looking for some insight and an assist (planning to test in-app purchase with TestFlight) - all works in Xcode. I have created my very first in-App purchases App (I have other paid apps in App store) Under Distribution tab in the Monetization section i created the in-app purchases item. I completed all fields and the status is now changed from waiting fior metadata to ready to submit.. Per my readings the in-app purchase item would be reviewed with a new version of the App. I uploaded a new version, added sandbox tester and submitted it for review.. My App in TestFlight now shows status of Testing, but the in-App purchase still shows waiting for review. On the Distribution tab the Add for Review button is active but it seems a bit illogical for me to click it as the in-App purchases is the only completed item on my App's distribution tab (I am not ready to submit for review yet..) So as illogical as it appears, is this the way to get your first in-App purchase approved?

When tapping the currently selected time in a TimePicker (wheel style) component to invoke the inline numeric pad popover, the popover renders incorrectly on iPadOS 26.4.1 — it appears as a very narrow single-line/bar rather than the full numeric keypad layout. Steps to Reproduce: Run Reminder, create a new reminder and add a custom time Tap the currently selected time value to trigger the numeric pad popover Observe the popover layout Expected Result: A properly sized popover appears containing a full numeric keypad, allowing direct numeric input of the time value — consistent with behavior on iPadOS 18.x Actual Result: The popover appears as an extremely narrow horizontal bar (single line height), making the numeric pad unusable Regression: Works correctly on iPadOS 18.x through iPadOS 26.3. Broken on iPadOS 26.4.1 (Xcode 26.x simulator and/or physical device). https://www.youtube.com/shorts/bd3pYA3B-iI https://www.youtube.com/shorts/wSHzepHBwEY Feedback: FB22517457