# Publishing to App Store Problems

**URL:** https://community.thunkable.com/t/publishing-to-app-store-problems/1357046
**Category:** Questions about Thunkable X
**Tags:** beginner
**Created:** [June 22, 2021, 12:54am UTC](https://community.thunkable.com/t/publishing-to-app-store-problems/1357046 "2021-06-22T00:54:12Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![3ncircle](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/3ncircle/32/28927_2.png) [@3ncircle](https://community.thunkable.com/u/3ncircle)
#### Post date: [June 22, 2021, 12:54am UTC](https://community.thunkable.com/t/publishing-to-app-store-problems/1357046/1 "2021-06-22T00:54:13Z")

</div>

Tried to publish a social networking app via App Store Connect. It was rejected for the reasons given below. The first issue is moot. The system has a blocking function. The other issues are beyond my scope of abilities. Any thoughts or suggestions?

From Apple

- 
  1. 2 Safety: User Generated Content

- 
  1. 1.1 Legal: Privacy - Data Collection and Storage

- 
  1. 8 Design: Sign in with Apple

### Guideline 1.2 - Safety - User Generated Content

We found in our review that your app includes user-generated content but does not have all the required precautions. Apps with user-generated content must take specific steps to moderate content and prevent abusive behavior.

**Next Steps**

To resolve this issue, please revise your app to implement the following precautions:

- A mechanism for users to block abusive users

**Resources**

Learn more about our policies for user-generated content in [App Store Review Guideline 1.2](https://developer.apple.com/app-store/review/guidelines/#user-generated-content).

### Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

We noticed that your app requests the user’s consent to access the camera, but doesn’t sufficiently explain the use of the camera in the purpose string.

To help users make informed decisions about how their data is used, permission request alerts need to explain **and** include an example of how your app will use the requested information.

**Next Steps**

Please revise the purpose string in your app’s Info.plist file for the camera to explain why your app needs access and include an example of how the user’s data will be used.

You can modify your app’s Info.plist file using the property list editor in Xcode.

**Resources**

- See examples of [helpful, informative purpose strings](https://developer.apple.com/ios/human-interface-guidelines/app-architecture/requesting-permission/).
- Review a list of [relevant property list keys](https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW18).

### Guideline 4.8 - Design - Sign in with Apple

Your app uses a third-party login service, but does not offer Sign in with Apple. Apps that use a third-party login service for account authentication need to offer Sign in with Apple to users as an equivalent option.

**Next Steps**

Please revise your app to offer Sign in with Apple as an equivalent option for account authentication.

Any help is appreciated!

---

<div class="post-metadata">

### Author: ![jane](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jane/32/27575_2.png) [@jane](https://community.thunkable.com/u/jane)
#### Post date: [June 22, 2021, 9:38am UTC](https://community.thunkable.com/t/publishing-to-app-store-problems/1357046/2 "2021-06-22T09:38:39Z")

</div>

Hi there,

For the first piece of feedback, you need to build some mechanism so that if A blocks B, B cannot view A’s profile or contact A through your app. B’s content should also be hidden from A by default. Many services would give A the option of viewing B’s content/profile, but I don’t think this is a necessary feature.

What purpose string do you currently give in your Camera Permissions section of your [project settings](https://docs.thunkable.com/v/drag-and-drop/projects/project-settings#ios-permissions)?

Does your app only offer Firebase sign in, or have you integrated some other sign in service as well?

---

<div class="post-metadata">

### Author: ![3ncircle](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/3ncircle/32/28927_2.png) [@3ncircle](https://community.thunkable.com/u/3ncircle)
#### Post date: [June 22, 2021, 9:31pm UTC](https://community.thunkable.com/t/publishing-to-app-store-problems/1357046/3 "2021-06-22T21:31:54Z")

</div>

As for the blocking feature, it’s already taken care of. With regard to purpose strings, how exactly do I add them? I added the camera as an invisible element but there is no way to input a the purpose string there. Any suggestions? As for the sign on, I will be working to develop it shortly.

---

<div class="post-metadata">

### Author: ![jane](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jane/32/27575_2.png) [@jane](https://community.thunkable.com/u/jane)
#### Post date: [June 23, 2021, 10:23am UTC](https://community.thunkable.com/t/publishing-to-app-store-problems/1357046/4 "2021-06-23T10:23:40Z")

</div>

You can enter purpose strings for components such as the Camera in your Project Settings.

Open the Settings tab, and scroll to iOS permissions. You should see a field where you can input a purpose string for your Camera.

 ![Screen Shot 2021-06-23 at 11.23.28 AM](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/6/f/6f00573bb5a3e7d4a1439988cd4d427cf17c2c98.png)

---

<div class="post-metadata">

### Author: ![wpp.appbookxgaxd](https://avatars.discourse-cdn.com/v4/letter/w/85f322/32.png) [@wpp.appbookxgaxd](https://community.thunkable.com/u/wpp.appbookxgaxd)
#### Post date: [January 26, 2023, 2:08am UTC](https://community.thunkable.com/t/publishing-to-app-store-problems/1357046/5 "2023-01-26T02:08:22Z")

</div>

I have that problem,  
I enter purpose strings but it not work?

How to solve problem?

 ![Screenshot 2023-01-26 090528](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/1/8/181a340e8915189d6dbc166e096781c92d914be9.png)  
 ![Screenshot 2023-01-26 090647](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/6/8/68d80392e2f1cd4e9e380a9afb58b31458462a52.png)

---

<div class="post-metadata">

### Author: ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)
#### Post date: [January 26, 2023, 3:02am UTC](https://community.thunkable.com/t/publishing-to-app-store-problems/1357046/6 "2023-01-26T03:02:02Z")

</div>

You have a short, somewhat vague explanation (“Record Voice and sound”). Did you click on the “helpful, informative purpose strings” link to see examples? What did you find there? Can you share that link?

What exactly do you use the microphone for in your app and how does that data get used, stored and shared?

---

<div class="post-metadata">

### Author: ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)
#### Post date: [November 8, 2024, 1:20pm UTC](https://community.thunkable.com/t/publishing-to-app-store-problems/1357046/7 "2024-11-08T13:20:07Z")

</div>


