Posts

Post marked as solved
1 Replies
0 Views
Replied In Constraints
OK I figured it out. Changed the layout to inferred and now it works.
Post marked as solved
4 Replies
0 Views
It does not allow me to add constraints (it is greyed out) because the map is now "part" of the UITableViewController
Post marked as solved
3 Replies
0 Views
Solved with this: let predicateString = "Lat BETWEEN {" + String(currentPlaceLat - limit) + ", " + String(currentPlaceLat + limit) + "}" + " && " + "Long BETWEEN {" + String(currentPlaceLong - limit) + ", " + String(currentPlaceLong + limit) + "}"
Post marked as solved
3 Replies
0 Views
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.
Post marked as solved
1 Replies
0 Views
Oversight... Record type was int when it should have been string. Solved!
Post marked as solved
1 Replies
0 Views
Problem was the injection of the dependency. Moving the code from the separate .Swift file to the main ViewController solved it.
Post marked as solved
3 Replies
0 Views
OK, I created a new container and now it connected. Seems like it was, after all, a problem on Apple's side?