build disappears

I posted https://developer.apple.com/forums/thread/809481 yesterday about an issue I discovered with pushWindow in visionOS 26.2 RC, but today I discovered a second problem with pushWindow. If window A calls pushWindow to present window B, and the user pins window B to a wall, the following unexpected behaviors are observed: Window B spontaneously disappears. If the user re-launches the (still running) app from the visionOS home view, both window A and window B appear simultaneously. I assume only window B should be visible at this point, since window A pushed window B. If the user closes window B, it's now impossible to present window B again. Calls to pushWindow appear to be ignored. If the user force-quits the app and relaunches it, and pushWindow is called again, window B appears, but window A remains visible. I also noticed this surprising behavior: This broken state of pushWindow behavior now affects all other apps on the system that may call pushWindow in the future, not just the app whose pus

Hello everyone, I’m an iOS developer from Türkiye, and I’m currently facing a serious issue regarding my Apple Developer account termination (Appeal Ticket: APL255848). Problem: I have removed all references, icons, descriptions, and metadata related to my previous app name (“Nano Banana”) both inside the app and on the App Store listing. I submitted updated assets, screenshots, and a new metadata package. However, the App Review Board seems to still be seeing old cached metadata, old icons, or previous descriptions that no longer exist in my build. Because of this, every response from App Store Connect repeats the same text, even though I have already made and proven all required changes. Current Situation: My account is terminated, and my appeal has been pending for over 3 weeks with identical non-actionable responses. I am not receiving my revenue for the past 2 months. I want to comply fully with the Apple Developer Program Agreement and provide any documents required (invoices, trademarks, API i

Can anyone please confirm that Apple-hosted Background Assets still will NOT work unless the app is: Installed from TestFlight, or Installed from the App Store Is it true Xcode-installed builds—Debug or Release—do not receive the App Store’s Background Asset metadata and cannot access the background asset packs? I am getting the error when running the app in Xcode: The asset pack with the ID “VALIDPACKNAME” couldn’t be looked up: No asset pack with the ID “VALIDPACKNAME” was found.

Hi there, I'm trying to work on an architecture where one app exposes an API (Extension Host) that other apps can plugin to. I've been reading all I can from the docs and whatever I can find online. It seemed like iOS26 added the ability to do such a thing (at least in early builds). Is that the case? Has the functionality been walked back such that extensions can only be loaded in iOS from within the single app bundle? My use case is the following: I'm working on an agent app that desires to have 3rd party developers add functionality (think how MCP servers add functionality to LLMs). The 3rd party plugins would be provided in their own app bundles vetted by the AppStore review team, of course, and would only provide hooks, basically, the main app can use to execute functions or get state. This is the best thread I found on the topic, and the subtext is that it needs to be in the same bundle. https://developer.apple.com/forums/thread/803896?answerId=865314022#865314022 Let's say for the moment that

Hi... It would be nice if Apple / XCode would be so gracious to explore the possibility of providing the ability to include: Code scrambling / renaming Control-flow obfuscation String encryption Anti-debugging Anti-hooking Jailbreak detection App integrity checks Runtime tamper detection That way, we could eliminate the need to settle for third-party software. Who do we have to bribe to submit such a request and entertain such an idea?

I’ve been building iOS apps since 2011, took a 4-year break, returned with two new apps, and it feels like organic visibility and indexing have changed drastically compared to earlier releases. Has anyone else noticed slower indexing, fewer automatic mentions, and almost zero organic traction—has discovery changed, or is it just saturation?

Hi everyone, I’m working on an iOS app that uses a Core ML model to run live image recognition. I’ve run into a persistent issue with the mlpackage not being turned into a swift class. This following error is in the code, and in carDetection.mlpackage, it says that model class has not been generated yet. The error in the code is as follows: What I’ve tried: Verified Target Membership is checked for carDetectionModel.mlpackage Confirmed the file is listed under Copy Bundle Resources (and removed from Compile Sources) Cleaned the build folder (Shift + Cmd + K) and rebuilt Renamed and re-added the .mlpackage file Restarted Xcode and re-added the file Logged bundle contents at runtime, but the .mlpackage still doesn’t appear The mlpackage is in Copy bundle resources, and is not in the compile sources. I just don't know why a swift class is not being generated for the mlpackage. Could someone please give me some guidance on what to do to resolve this issue? Sorry if my error is a bit naive, I'm pretty new