Got reject because of UIBackgroundmodes and MIDIDestinationCreate and

Question

Created Sep ’17

Replies 4

Boosts 0

Views 1.8k

Participants 4

Hi,

I've got rejected (by reviewers and appeal) due-to UIBackgroundmodes with audio but it doesn't play anything in the background. The problem is my app uses UIBackgroundmodes audio because of MIDI method which plays sound (method: MIDIDestinationCreate). Apple documentation clearly states that this method requires this attribute:

https://developer.apple.com/documentation/coremidi/midi_services

Beginning in iOS 6, apps need to have the audio key in their UIBackgroundModes in order to use CoreMIDI’s
MIDISourceCreate(_:_:_:)
and
MIDIDestinationCreate(_:_:_:_:_:)
functions. These functions return kMIDINotPermitted (-10844) if the key is not set.

I've found the same thread where a developer says that Apple developer support team doesn't see any problems with this approach and MIDIDestinationCreate method indeed requires UIBackgroundmodes. So it was a mistake and he was finally approved by appeal team:

https://stackoverflow.com/a/24975134/1389546

Any ideas how to resolve it?

Boost

Answer 1

songtive OP

Sep ’17

Accepted Answer

For anyone who is looking for the solution. With each appeal request (I've got about 5 rejects) I've described in details that it's a mistake and the application shouldn't be rejected. So I decided to submit DTS request and got a reply:

DTS has forwarded the information you provided to the App Review Team at Apple. In the future when going through the appeal process, be sure to reference information from Apple documentation.

The App Review team will look over your app submission and may follow up with you if there are any questions.

Five hours later we received approve!

0

Answer 2

mattharg OP

Oct ’17

Since the rejections you received were bogus, did Apple refund the charge associated with the DTS?

0

Answer 3

MendelK OP

Oct ’17

I got refunded a DTS request once when you ask nicely if the reason for the request was not your fault.

0

Answer 4

Crudebyte OP

Oct ’17

We also had the exact same issue with app review before. Like others already said, what you are doing is legitimate.

To avoid this issue in future: on iTunes Connect, when you access your app description there, there is a text field "App Review Information" -> "Notes". Add the reference to the API docs and reasoning in that text field. Such that each time your app goes into review in future, the reviewers can immediately see the reason why you are using this capability.

0