Just when I think I am finally starting to understand Swift I come across a gotcha like the following: I have two object, a swiftui display and one of data to be displayed. Ok, sounds easy. The data is read out of a JSON file so I have a set of arrays and dictionaries. The data is valid when read, it is definitely there, but when I go to display it, its gone. Just vanished. Wasted about a day on this so far, and I’ve seen it before, the inability to pass out of an object an array or dictionary with contents intact. If I create an array var, and not let the system do it, contents are preserved. So, in the data object I’ll have something like this: struct DataObject{ var item: [String:Any] item=JSONData serialized out of memory, and may have say, 12 fields } In my SwiftUI module I have: var item=dataObject.item dataObject.item now has 0 fields. I can allocate and initialize a dictionary in DataObject and those elements come through fine. So it seems like the stuff being serialized from JSON is being deleted out from under me.

Anyone else experiencing longer than normal review times? Right now it's five days and counting. I surmise that maybe ppl may be taking early Christmas vacations.

I am shown as being subscribed to our service in the Subscriptions list in settings yet when going to the Storekit2 page in my app it shows me as NOT being subscribed and is unresponsive. I select Restore Subscription, that grays briefly, asks for a password, then returns to blue and nothing else happens. Bouncing back and forth between monthly and yearly likewise gives no response. The Transaction.currentEntitlements seems to be empty so it thinks the user is not subscribed. I have unsubscribed, and resubscribed via the Settings page to no avail.

My startup screen (not using a formal splash screen) opens up and almost immediately jumps to the right about 50 pixels. Not sure if this is notch related but I suspect it is. Any ideas?

I've been pouring over the code for Apple's visionOS demo: "Destination" trying to figure out something about its skybox. (not really a box, there, Apple). The skybox contains a 360deg panorama, but only one half shows with the other half fades out to nothing. I cannot find anywhere there is an alpha channel being set, a lighting or material effect causing that. But "alpha" doesn't show up and the only gradients are use to make controls standout a little more in its window. I need a full panorama that shows., no fading.

I've been working on a project with App Intents and have hit a complete wall. The desire is to have an app that allows a person to place an order of something and have that order processed while in lock screen without any intervention. Is that workflow possible without having to unlock the screen? Under what circumstances can a task be handled without unlocking the device. Going over some of the documentation about older custom intents strongly implies that this was possible under certain circumstances.

We're using App Intents to launch are control our app via Siri. Siri's responses have been fairly random, some with a "Done" popup, others with a verbal confirmation, others saying "I'm sorry, there's been a problem". The latter is bogus and doesn't look good to potential investors when the app is actually working fine. There appears to be no way in code that I've been able to find so far that would have been tell Siri to STFU. Let us handle our own errors. Otherwise is there a means to supply Siri with a dictionary of restored messages that could be triggered inside the app?

I'm trying to submit a build to external test for some important investor demos but the Submit button has vanished. Been like that for several hours and we really need to get this out. Has it moved somewhere?

I am not having any luck mutating a var in a structure, and yes, the method is defined as 'mutating' here's the struct definition: struct OnboardingSwipeableView: View{ static var shared = OnboardingSwipeableView() @State var currentPage = 0 var lock = NSLock() <snip> here's the method: mutating func goToNextPage(){ currentPage = self.currentPage+1 print("OBM->goToNestPage: currentPage=\(self.currentPage)") } however currentPage is not being updated. What gives?

I'll ask Siri: What is the weather?" and will get a valid response I'll ask Siri to execute a shortcut my app has created I get "what is the order?" (a phrase nowhere in my app) I'll repeat the question about the weather I now get "what is the order?" ***?

I recently released an update for one of my apps and am seeing precisely 0 updated downloads. I should be seeing thousands. I am getting sales, though.

I have an iPhone VR app, but on the appstore page it says "Compatible with iPad". The full VR effect was only with the iPhone, but it's not showing that, nor is there any apparent way to set that in the metadata. So I am assuming that's automated. Any ideas how to fix it?

In prep for a push this evening did the usual clean and rebuild. But now I'm getting errors that it can't find files with .swiftdoc, swiftsourceinfo, and swiftmodule files. The few postings I can find about that said that reinstalling xcode fixed it, well , not i my case. Any ideas short of reconstructing the entire project from scratch?

I am in a weird twilight-zone of a git problem in xcode. I specify some files to be staged and it fails to do with no warning of any sort. So I cannot commit them or apply stashed changes to them. I can do it one.file.at.a.time. I have over 11k intermediate files that .gitignore won't ignore, nor stage nor commit to do anything so I could stop tracking them.

I am working on an app that links into Siri with Appintents. The user gives a command, the app is launched, does some magic and returns, via Siri ,custom success or fail messages. Most of the time. However, sometimes Siri kicks in its own "Something went wrong, please try again message". But something hasn't gone wrong. How can I stop those and ensure our own messages dependably make it through, regardless. The only thing is that there might be timeout issue, but usually our operation is completed after only a couple of seconds. Doesn't look good during investor demos.