iOS SDK Example app always displays "Transaction was unsuccessful" even though transaction succeeds

[TonyC5]

Example app included with iOS in-person SDK and our custom app both always generates "Transaction was unsuccessful" alert dialog when operating in LIVE Mode (not Sandbox). Despite the "Transaction was unsuccessful" alert message, the transaction ends in state "AuthorizedPendingCapture" (which is what we want). Details are below and are repeatable and consistent.

We have developed a custom app with the iOS in-person SDK. When we switched from Sandbox testing to Live Mode testing, the SDK always displays the alert dialog "Transaction was unsuccessful" after the credit card is inserted in the EMV chip reader and processed. Despite this "unsuccessful" message, we confirm that the client transaction always ends in state "AuthorizedPendingCapture" (which is what we want, since our server completes the transaction by submitting a Capture request).

We have confirmed that this same "Transaction was unsuccessful" message is displayed by the Example app that is included with the iOS in-person SDK, so we know that this is not a problem specific to our custom app. When the Example app is run in Live mode with Live Transaction Manager credentials, the Example app displays "Transaction was unsuccessful" after the credit card is inserted in the chip reader. This behavior is repeatable and consistent. It happens during EVERY credit card transaction and happens with both our custom app and the iOS SDK Example app when configured in LIVE mode with LIVE Transaction Manager credentials.

How do we eliminate the "Transaction was unsuccessful" alert dialog displayed by the SDK? Note that we want the finished client transaction to remain with status AuthorizedPendingCapture, because we need to complete the transaction with a Capture request from our server. We do not want the client to submit CapturedPendingSettlement transactions. We only want to eliminate the "Transaction was unsuccessful" message.

Details about our system are below.

• Client devices / operating systems: iPhone 4s (iOS 9.3.6), iPhone 5s (iOS 12.5.5), iPhone SE Generation 1 (iOS 13.7) (all of these devices / iOS versions exhibit the "unsuccessful" behavior described above)
• Credit card reader (from partner.posportal.com): BBPOS Chipper 2X Audio Jack (all devices ordered in March 2019 and August 2021 exhibit the "unsuccessful" behavior described above)
• Authorize.Net operation mode: Live (NOT Sandbox). We are testing and producing this error with a LIVE system and real credit cards
• Authorize.Net user type for the client (mobile) app: Transaction Manager with the only processing permission "Create charge transactions" - the configured user has no other transaction processing permissions
• Credit card type: Visa EMV (we are only testing the chip reader and we are not swiping credit cards)

Thank you for your help.

[TonyC5]

We reported this issue as a case opened with Authorize.Net support. After 5 months of responding to Authorize.Net requests for more information, our case was closed without notifying us. After we inquired as to the reason for case closure, we were told that we need to seek support in this forum.

Is there something else we are supposed to do to report problems and receive support for the Authorize.Net IOS SDK?