MFi needed when only linking against ExternalAccessory framework

Question

Created Dec ’17

Replies 3

Boosts 0

Views 1.2k

Participants 2

We are developing an App that uses the Epson SDK for iOS. The framework requires us to link against the External Accessory Framework, even if we only connect to Wi-Fi printers; but the same connection call would allow us to connect to Bluetooth printers (there's just one parameter to change in the function call). So the question is, do we need an MFi approval? What happens if we link against this framwork and simply don't include the UISupportedExternalAccessoryProtocols key? How does Apple know whether the app actually connects to a bluetooth device if there is only one framework for all (Wi-Fi and Bluetooth) and only one function to call (where you can set one parameter to either Wi-Fi or to Bluetooth)?

Answered by NotMyName in 284493022

What MFi approval? Who do you think you need approval from?

Disclaimer: If Epson's engineers messed up (by, for instance, setting up their SDK to require the External Accessory framework instead of weak linking so you don't need it), and their SDK causes some problem for you during review, you'll have to contact them when you discover the issue.

Boost

Answer 1

NotMyName OP

Dec ’17

UISupportedExternalAccessoryProtocols is a software limitation (it enables protocols), not something that you need to use to tell App Review what you're doing. So if you don't need it to work then you don't include it.

0

Answer 2

tomodyne OP

Dec ’17

Well okay. But what about the MFi approval?

0

Answer 3

NotMyName OP

Dec ’17

Accepted Answer

What MFi approval? Who do you think you need approval from?

Disclaimer: If Epson's engineers messed up (by, for instance, setting up their SDK to require the External Accessory framework instead of weak linking so you don't need it), and their SDK causes some problem for you during review, you'll have to contact them when you discover the issue.

0