OK, I created a new container and now it connected. Seems like it was, after all, a problem on Apple's side?
leo008
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Toronto, ON
Post
Replies
Boosts
Views
Activity
Problem was the injection of the dependency.
Moving the code from the separate .Swift file to the main ViewController solved it.
Oversight...
Record type was int when it should have been string.
Solved!
Yes, I know, but I’m avoiding them because I need more precision and I understand these have a 10km precision. Thanks. I want to implement in the way I described.
Solved with this:
let predicateString = "Lat BETWEEN {" + String(currentPlaceLat - limit) + ", " + String(currentPlaceLat + limit) + "}" + " && " + "Long BETWEEN {" + String(currentPlaceLong - limit) + ", " + String(currentPlaceLong + limit) + "}"
It does not allow me to add constraints (it is greyed out) because the map is now "part" of the UITableViewController
OK I figured it out. Changed the layout to inferred and now it works.