2

I'm doing a project that deals with a MapKit. My issue is when I run the app, I get the 'Could not inset legal attribution from corner 4.' error. What solution can I take to resolve this issue?

error:

My app screen:

  • 1
    Ignore it. It is an internal debugging message from the mapView around placing the "legal" link ta the bottom of the map. – Paulw11 Feb 11 '18 at 19:49
  • How do I get my app running right? Do I need to comment out something in my code? –  Feb 11 '18 at 21:26
  • You haven’t explained what your problem is. This message doesn’t mean anything. – Paulw11 Feb 13 '18 at 00:45
  • My map doesn't display when I run it on the simulator. My blue location dot shows up, but my map doesn't. –  Feb 13 '18 at 04:17

2 Answers2

2

I had the exact same error as you - the map was not showing up and I was getting the error:

2018-08-25 09:59:17.324966-0400 Parse Foursquare Clone[45537:42276733] Could not inset legal attribution from corner 4

2018-08-25 09:59:17.332612-0400 Parse Foursquare Clone[45537:42276733] Could not inset scale from edge 9

The reason is because I did not setup the delegates, MKMapViewDelegate and CLLocationManagerDelegate. Here is what I'm looking at in case you're confused. Once I set these up, the map started appearing. Hope this helps!

import UIKit
import MapKit
import CoreLocation

class locationVC: UIViewController, MKMapViewDelegate, CLLocationManagerDelegate {
Lionel Yu
  • 328
  • 3
  • 11
-2

Re-edit the info.plist file. Open As -> Source Code To show the XML format of info.plist

Your xCode error message may say the the "NSLocationAlwaysUsageDescription" or "NSLocationAlwaysAndWhenInUseUsageDescription" has problem.

COPY the "NSLocationAlwaysUsageDescription" (or "NSLocationAlwaysAndWhenInUseUsageDescription") in error console and PASTE to the info.plist source file.

Save the info.plist and run it again.

I do it this way and resolved my problem

Kuang-Der Wu
  • 1
  • 1
    This is not what is causing the inset legal attribution error. I can reproduce the error and have NSLocationWhenInUseDescription set properly. – Big-O Claire Jul 23 '18 at 19:54