# \[Solved\] Map Component and iOS 5.1.1 Rejection **URL:** \ **Category:** Publishing\ **Tags:** publish, map, apple\ **Created:** [June 27, 2024, 5:45pm UTC](https://community.thunkable.com/t/solved-map-component-and-ios-5-1-1-rejection/3077431 "2024-06-27T17:45:07Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![christian.noblem](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@christian.noblem](https://community.thunkable.com/u/christian.noblem)\ **Post date:** [June 27, 2024, 5:45pm UTC](https://community.thunkable.com/t/solved-map-component-and-ios-5-1-1-rejection/3077431/1 "2024-06-27T17:45:07Z")
I received a publication rejection from Apple based on 5.1.1, which denotes a lack of specific language regarding location access. \*Issue Description One or more purpose strings in the app do not sufficiently explain the use of protected resources. Purpose strings must clearly and completely describe the app’s use of data and, in most cases, provide an example of how the data will be used.\* I’ve followed the instructions here: [Tracking Usage Description | Thunkable Docs](https://docs.thunkable.com/publishing-apps/publish-to-app-store-ios/tracking-usage-description) regarding location components. ![Ad Hoc Tracking Description](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/5/f/5f7a675a4c0a67db3996a3191f1626d11bd8a164.jpeg) But I’ve noticed the language doesn’t update as expected. The generic language Apple does not like remains: **Your projects may access your location.** ![Location Message](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/3/e/3ea4b3151137ca748ea42c1feaf999504a3e9be2.jpeg) Thoughts? The project can be found here: [Thunkable](https://x.thunkable.com/projects/63ed22dea68ff04642523f41/35c88709-be36-4208-a7d1-be8e4bd325ce/designer) ---
**Author:** ![matt\_conroy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/matt_conroy/32/150843_2.png) [@matt\_conroy](https://community.thunkable.com/u/matt_conroy)\ **Post date:** [June 28, 2024, 1:49pm UTC](https://community.thunkable.com/t/solved-map-component-and-ios-5-1-1-rejection/3077431/2 "2024-06-28T13:49:16Z")
Hi @christian.noblem, thanks for reaching out. We discussed this issue in a separate support channel but I also wanted to offer the answer here. The issue here is not with the location tracking dialog, your app also contains a web viewer component and when those are used, you must disclose to the end user of your app, that by visiting the site in the web viewer, that site may track users in some way. The [recommended string to include](https://docs.thunkable.com/publishing-apps/publish-to-app-store-ios/tracking-usage-description#h_66addfaf59) for this is: `This app accesses [X] website. Your data may be shared with this website to facilitate functionality.` What you’ve entered in the User Tracking Usage Description pertains to the location sensor and so Apple is saying that the tracking description is not clear about tracking vis a vis the web sites shown in the web viewer. When a location sensor is present in your app, it will automatically add in a dialog for determining location (precise or approximate). We have tested the phrasing used “Your projects may access your location” for this and it is acceptable for the Apple review process. For the tracking, you would want to enter something that accounts for the web viewer and location sensor ([get current location](https://docs.thunkable.com/blocks/app-features/sensors-blocks/location-sensor#get-current-location) block): “This app accesses [name of site] website. Your data may be shared with this website to facilitate functionality. When you share your location, this app uses your location to show you the closest available court resources.” ---
**Author:** ![christian.noblem](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@christian.noblem](https://community.thunkable.com/u/christian.noblem)\ **Post date:** [July 1, 2024, 2:28pm UTC](https://community.thunkable.com/t/solved-map-component-and-ios-5-1-1-rejection/3077431/3 "2024-07-01T14:28:20Z")
I included the following language in the Tracking Usage Description, “This app accesses court-adjacent websites. Your data may be shared with these websites to facilitate functionality. When you share your location, this app uses your location to show you the closest available court resources.” Which they triggered and included a screenshot: ![IMG_0057](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/f/3/f3863e7fce40fa2514dc1daa7b109ad8ec3dd19c.jpeg) But has anyone had an app with the mapping component approved with the below language on the map tracking pop-up? ![IMG_0059](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/5/f/5fa8b6e01e77eaec408b2fe9bdb133ea2bc69e0d.jpeg) ---
**Author:** ![christian.noblem](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@christian.noblem](https://community.thunkable.com/u/christian.noblem)\ **Post date:** [July 1, 2024, 6:56pm UTC](https://community.thunkable.com/t/solved-map-component-and-ios-5-1-1-rejection/3077431/4 "2024-07-01T18:56:52Z")
This has been solved. There is an iOS Permissions field that is supposed to appear when you add a Current Location data block. ![ios](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/4/e/4e0133dd95b0359468fb8e229a65ffae693a5abc.jpeg) The solution was to remove and re-add the data block. This forced the field to show up in Settings. I’ve done this, added the prior language, and this is no longer an issue. ---
**Author:** ![matt\_conroy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/matt_conroy/32/150843_2.png) [@matt\_conroy](https://community.thunkable.com/u/matt_conroy)\ **Post date:** [July 1, 2024, 7:04pm UTC](https://community.thunkable.com/t/solved-map-component-and-ios-5-1-1-rejection/3077431/5 "2024-07-01T19:04:49Z")