Thanks for the response. I should have provided some more details. My app is not crashing or being terminated by iOS. I know this because the user says that when they open the app later, it opens immediately to the screen where they left off. If it had crashed it would have started at a login screen. The app is designed to store location updates locally until the user is ready to send them to the server, but I'll check to see if something else might be using Wifi. I hadn't considered that it might be taking too long to process updates. I'll look into that. I think all it's doing is storing them in a SQLite database.

Class B is Codable as a consequence of extending class A. If you try to mark it Codable explicitly, it's a compiler error. You can mark B Codable instead of A, but then A.x won't decode. The json just says { "x": "foo", "y": "bar" }. If you put x and y into one class it decodes fine.

Thanks for the response. I checked my code and found that I had already implemented the isEqual method but forgot to mention it in my original post. Oddly, my app compiles and runs now even though I did not really change anything. Also oddly, when I build it I see the "Redundant conformance to Hashable" message show up for a moment, and then disappear. Possibly this is some kind of Xcode bug? It doesn't really matter at this point I guess. I'd feel better knowing why it happened initially but I can't really expect anyone to spend time debugging an Objective-C issue. Frank

I was never able to fix this, but I was able to determine that the error was coming from a build script associated with 'Cocoapods'. I decided to remove all of the Cocoapods stuff from the project and replace it with Swift packages, which fixed the problem.

Thanks for the response. The error is gone now. I didn’t change my code. I probably did a clean rebuild or restarted Xcode.

My app actually still runs. I think this is just a bug with the editor incorrectly flagging an error. The superclass in this case is an Objective-C class so maybe that has something to do with it.

Basically I'm swiping down from the top edge of the view. This is the only time I see the problem. If I close the view by calling dismiss myself (for example if I put a cancel button in the view), it works fine. I don't really need or care about the swipe-to-close behavior. Can it be disabled?

Thanks for the response. Actually, the problem was that my code was calling "setValue" instead of "set", which I guess happened because I chose the wrong autocomplete and didn't notice it right away. Once I fixed that it worked as expected.

12 days later I'm still experiencing this problem, so I don't think it's a transient issue with the app store servers. I have a followup question though. I've been doing iOS development since 2009. For many years, I have posted in these forums and gotten lots of timely help, often from Apple employees. I really appreciate that. Most other companies pay very little attention to their user forums. But ever since Apple changed the format of these forums last year, I have gotten no responses to anything I have posted. I am wondering, am I doing something wrong, not using tags correctly, etc? Or is this simply the new reality? Frank