Apple application rejected because of few references to a pre-release version of Apple software

Question

Created Sep ’22

Replies 1

Boosts 0

Views 1k

Participants 2

In order to prepare our live mobile application compatibility with upcoming ios16 release we tested with ios beta versions available. We found one bug in app because of which application was crashing.

We fixed the bug and now want to release in production before ios16 is available on devices. So that if our customers upgrade their phones they should not get crash. We mentioned the same details in metadata of whats new section while publishing. But apple rejected saying there are few references to pre-release version of Apple software, products, or hardware which is not in compliance with the Apple Developer Program License Agreement.

My questions is, if we want to release the application which is ios16 ready then what approach should be followed? What should be updated in metadata?

Boost

Answer 1

endecotp OP

Sep ’22

if we want to release the application which is ios16 ready then what approach should be followed? What should be updated in metadata?

There are a few things that you must never mention in the app metadata. In particular, things like this will be rejected by Apple:

Includes a workaround for a bug in iOS.
Supports a new iOS version that's still in beta.
Can now share data with our Android app.
Some previously paid features are now free.

The solution is simple, just don't mention those things. Write a vague "what's new" message like "Miscellaneous bug fixes".

0