# Apple Store Review:

**Review Environment**

Submission ID: bd8a8343-a607-4203-a53b-e791fcb9477d

Review date: March 27, 2024

Version reviewed: 1.0

### **Guideline 1.5 - Safety**

***1.5 Developer Information***

*People need to know how to reach you with questions and support issues. Make sure your app and its Support URL include an easy way to contact you; this is particularly important for apps that may be used in the classroom. Failure to include accurate and up-to-date contact information not only frustrates customers, but may violate the law in some countries or regions. Also ensure that Wallet passes include valid contact information from the issuer and are signed with a dedicated certificate assigned to the brand or trademark owner of the pass.*

**Issue Description**

The Support URL provided in App Store Connect,

[https://matework.ch](https://matework.ch/)

, does not direct to a website with information users can use to ask questions and request support.

**Next Steps**

Update the specified Support URL to direct users to a webpage with support information.

**Resources**

Learn about Support URLs and other platform version information on

[App Store Connect Help](https://developer.apple.com/help/app-store-connect/reference/platform-version-information/)

.

### **Guideline 2.1 - Performance**

***2.1 App Completeness***

*Submissions to App Review, including apps you make available for pre-order, should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission. Make sure your app has been tested on-device for bugs and stability before you submit it, and include demo account info (and turn on your back-end service!) if your app includes a login. If you are unable to provide a demo account due to legal or security obligations, you may include a built-in demo mode in lieu of a demo account with prior approval by Apple. Ensure the demo mode exhibits your app’s full features and functionality. If you offer in-app purchases in your app, make sure they are complete, up-to-date, and visible to the reviewer, or that you explain why not in your review notes. Please don’t treat App Review as a software testing service. We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems.*

**Issue Description**

The app exhibited one or more bugs that would negatively impact App Store users.

Bug description: an error message appeared when we attempted to Sign in with Apple.

Review device details:

- Device type: iPad Air (5th generation)
- OS version: iOS 17.4.1

**Next Steps**

Test the app on supported devices to identify and resolve bugs and stability issues before submitting for review.

If you are unable to reproduce the bug, try the following:

- For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce.
- For app updates, install the new version as an update to the previous version, then follow the steps to reproduce.

**Resources**

- For information about testing apps and preparing them for review, see

[Testing a Release Build](https://developer.apple.com/documentation/xcode/testing-a-release-build)

.

- To learn about troubleshooting networking issues, see

[Networking Overview](https://developer.apple.com/library/archive/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/Introduction/Introduction.html)

.

- Watch a video with

[tips for preventing common rejections](https://developer.apple.com/go/?id=ar-tips-1)

.

### **Guideline 2.1 - Information Needed**

We
have started our review, but we need additional information to
continue. Specifically, it appears your app may access or include paid
digital content or services, and we want to understand your business
model before completing our review.

**Next Steps**

Please review the following questions and provide as much detailed information about your business model as you can.

1. Who are the users that will use the paid services in the app?

2. Where can users purchase the services that can be accessed in the app?

3. What specific types of previously purchased services can a user access in the app?

4. What paid content, subscriptions, or features are unlocked within your app that do not use in-app purchase?

### **Guideline 2.3.10 - Performance - Accurate Metadata**

***2.3.10***

*Make sure your app is focused on the iOS, iPadOS, macOS, tvOS or watchOS experience, and don’t include names, icons, or imagery of other mobile platforms in your app or metadata, unless there is specific, approved interactive functionality. Make sure your app metadata is focused on the app itself and its experience. Don’t include irrelevant information.*

**Issue Description**

The
app or metadata includes information about third-party platforms that
may not be relevant for App Store users, who are focused on experiences
offered by the app itself.

Remove instances of this information
from the app and its metadata, including the app description,
promotional text, What's New info, previews, and screenshots.

**Next Steps**

Revise the app's screenshots to remove non-iOS status bar images and non-iOS menu bar images.

Revised
screenshots should accurately reflect the app in use on the supported
devices and highlight the app's main features in the majority of the
screenshots.

Reply to App Review in App Store Connect with
additional information if the app's functionality and how it interacts
with third-party platforms has been misunderstood.

**Resources**

Learn how to edit App Store metadata on

[App Store Connect Help](https://developer.apple.com/help/app-store-connect/get-started/app-store-connect-homepage)

.

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

***5.1.1(ii) Permission***

*Apps that collect user or usage data must secure user consent for the collection, even if such data is considered to be anonymous at the time of or immediately following collection. Paid functionality must not be dependent on or require a user to grant access to this data. Apps must also provide the customer with an easily accessible and understandable way to withdraw consent. Ensure your purpose strings clearly and completely describe your use of the data. Apps that collect data for a legitimate interest without consent by relying on the terms of the European Union’s GeneralData Protection Regulation ("GDPR") or similar statute must comply with all terms of that law.*

**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.

Examples of unclear purpose strings:

- "App would like to access your Contacts"
- "App needs microphone access"

**Next Steps**

Update
the photo library purpose string to explain how the app will use the
requested information and provide an example of how the data will be
used. See the attached screenshot.

**Resources**

- See examples of

[helpful, informative purpose strings](https://developer.apple.com/design/human-interface-guidelines/patterns/accessing-private-data)

.

- 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)

.

**Support**

- Reply to this message in your preferred language if you need assistance. If you need additional support, use the

[Contact Us module](https://developer.apple.com/contact/topic/#!/topic/select)

.

- Consult with fellow developers and Apple engineers on the

[Apple Developer Forums](https://developer.apple.com/forums/)

.

- Help improve the review process or identify a need for clarity in our policies by

[suggesting guideline changes](https://developer.apple.com/contact/app-store/?topic=guideline)

.