There are a handful of these "invalid_client" errors on this forum within the past few days. I suspect there has been a change on apple's end recently and it either a bug or has undocumented requirements that we're not fulfilling. We've burned about 12 man-hours on this today - a complete waste of time. If anyone can shed any light on this, that would be splendid. Thanks Luke

If you take a look on this forum, there are at least another 2 tickets on here for the same "invalid_client" issue. We've wasted loads of time on this too. See about keeping an eye on the wider forum in case another ticket gets some traction!

We got this resolved by going into the More Configure and adding our domain, making sure the SPF tick is green (if its not green, do a quick google to find out how to fix it for your config). After this, we stopped getting invalid_client errors. The thing that made us stumble on this was it didn't appear important on account of it saying it was for the emails - we skimmed over it thinking we could come back to it later..

We got this resolved by going into the More Configure and adding our domain, making sure the SPF tick is green (if its not green, do a quick google to find out how to fix it for your config). After this, we stopped getting invalid_client errors. The thing that made us stumble on this was it didn't appear important on account of it saying it was for the emails - we skimmed over it thinking we could come back to it later..

We got this resolved by going into the More Configure and adding our domain, making sure the SPF tick is green (if its not green, do a quick google to find out how to fix it for your config). After this, we stopped getting invalid_client errors. The thing that made us stumble on this was it didn't appear important on account of it saying it was for the emails - we skimmed over it thinking we could come back to it later..

Just to expand on @OOPer's comment and spell it out for simple-folk such as myself who are fairly new to SwiftUI - You don't need to "nest" a NavigationView. By that it means (including pseudo-code) View A -> View B View A var body: some View { NavigationView( .. stuff here .navigationBarTitle("Main menu") ) } View B var body: some View { Text("Stuff to show on the next page") .navigationBarTitle("sub menu", displayMode: .inline) } Seems kind of obvious when you think about it, coming from UIKit, you wouldn't be able to push a UINavigationController into the navigation stack.

I'm getting this very quickly in areas that require a lot of MKPolylineRenderer / MKPolygonRenderer / MKMultiPolygonRenderer. I have tried changing mapType on when moving about, before removing/adding new overlays, but it's just totally flaking out on iOS 16.1.1. This is kind of a critical issue for us as it's breaking our production application. Has anyone got any insight into this this recently?