I'm a freelancer in iOS development but every now and then I get a request to make small websites for distant relatives or friends or acquaintances of them. I don't like those heavy weight websites that take ages to load (hello WIX) with tons of js and those damned cookies. On the other hand I don't like to make static websites myself in html like in the 90s which look super sparse (though they load very fast). What I would really like is to make use of my Swift/SwiftUI knowledge in web. Been thinking about some minimal framework or some kind of method to do that. Found some toy projects but I don't want to bring the iOS L&F to the web, I want websites to look like websites but made with SwiftUI. No more CSS and HTML. Compiling SwiftUI to html is the first naive idea that comes to mind. But I lack the broad knowledge of web technologies out there so I find myself unable to devise anything that could nearly rival other sophisticated frameworks.

Have this too, I hope Apple can fix this server-side and whitelist Xcode 15.0.1 being a production version. I downloaded it directly from developer.apple.com, not from the App Store app.

I had this too, it works now with Xcode 14.1 Beta 3. But then later it complains with an unsupported SDK version for the App Store. PS: Correction, it does not work. There was a problem uploading a build which was solved, I referred to that. Sorry.

+1 Waiting for Xcode 14 update. Hope it'll come soon because I need to test the app on a real device before uploading for customer.

I am having the same problem with 404 and 1404 error codes. Sorry that I am of no help. The API documentation of NSBundleResourceRequest says "This class ignores calls from Mac apps built with Mac Catalyst." and I am wondering if this is also true for M1 apps designed for iPad.

I have the same issue like the OP, and it still exists in iOS 16 beta 2, whether I use NavigationSplitView or NavigationView with column-style. Are there no other view modifiers that are called? I have a singleton audio engine in the app, and the detail view initializes itself on the engine at .onAppear. Can't have a new audio engine for each detail view, especially if the previous detail view is not discarded.

Ok I'll answer my post myself: I have written my own audio "engine". It runs in my own effect plugin. In the render callback I can do whatever I want with the input channels. This means I have to invoke render callbacks of all generators and effects myself, and I have to mix buffers myself, Accelerate framework to the rescue.

Hi, I have the same issue, did you or Apple find a solution to this?

Hi, Apple Dev Support never got back to us. Hence, as a workaround, we simply created a new in-app purchase which is identical to the broken IAP except it has a new product identifier of course. The app still handles the old IAP in the receipt (for users who bought it in the past) but when the user taps the purchase button the app purchases the new IAP.