No able to add a new card using react-native-square-in-app-payments using prod and iOS simulator

Questions
1

I’m having issues to test in iOS simulator using production,

Simulator Screen Shot - iPhone 11 Pro Max - 2021-10-26 at 11.39.43
Simulator Screen Shot - iPhone 11 Pro Max - 2021-10-26 at 11.39.431242×2688 48.1 KB

This is when I tried to add a new card using -SQIPCardEntry.startCardEntryFlow and I got this error
“Error, something went wrong please contact the developer of this application and provide them with this error code: unexpected”

I’m using react native “react-native-square-in-app-payments”: “^1.6.0”, ios target - platform :ios, ‘12.0’
this just happens just in the simulator on the device works fine,
is anybody experience this error?

2

:wave: What is the error that is showing in your API Logs? :slightly_smiling_face:

3

Bryan Thanks for your prompt response, There is nothing in the logs yet I’m not calling to the endpoint to attach a payment method to the customer in square, I’m trying to generate cardNonce using “react-native-square-in-app-payments" which is using square SDK in the client.

4

What’s your application Id and what currency are you trying to charge in?

5

this is my application ID sq0idp-odgsWWzmgLDUgMOzHrOXKg

6

Are you getting this error with the emulator or is it loaded on the device. Also is there any terminal errors with more information?

7

just with iOS simulator, this is what I can see in the logs

what I can see is
2021-10-29 16:01:21.880997-0400 APP[6099:3926110] Can’t find keyplane that supports type 4 for keyboard iPhone-PortraitTruffle-NumberPad; using 25901_PortraitTruffle_iPhone-Simple-Pad_Default

2021-10-29 16:01:26.448652-0400 APP [6099:3936376] Received XPC error Connection interrupted for message type 3 kCFNetworkAgentXPCMessageTypePACQuery

2021-10-29 16:01:26.448871-0400 APP [6099:3936376] Received XPC error Connection invalid for message type 3 kCFNetworkAgentXPCMessageTypePACQuery

2021-10-29 16:01:42.306644-0400 APP[6099:3926110] Can’t find keyplane that supports type 4 for keyboard iPhone-PortraitTruffle-NumberPad; using 25901_PortraitTruffle_iPhone-Simple-Pad_Default

2021-10-29 16:03:28.899169-0400 APP[6099:3939103] Received XPC error Connection interrupted for message type 3 kCFNetworkAgentXPCMessageTypePACQuery

2021-10-29 16:03:28.899561-0400 APP[6099:3939103] Received XPC error Connection invalid for message type 3 kCFNetworkAgentXPCMessageTypePACQuery

8

Is the device that you are using one of the new M1 Mac’s?

9

No, I’m not using M1 Mac

find my react native info

System:
OS: macOS 11.4
CPU: (16) x64 Intel(R) Core™ i9-9880H CPU @ 2.30GHz
Memory: 1.33 GB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.17.6 - /usr/local/bin/node
Yarn: Not Found
npm: 8.0.0 - /usr/local/bin/npm
Watchman: 2021.06.07.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0
Android SDK:
API Levels: 27, 28, 29, 30
Build Tools: 28.0.3, 29.0.0, 29.0.2, 29.0.3, 30.0.2
System Images: android-26 | Google APIs Intel x86 Atom_64, android-27 | Intel x86 Atom_64, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64, android-28 | Google X86_ARM Intel x86 Atom, android-29 | Google APIs Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom_64
Android NDK: Not Found
IDEs:
Android Studio: 4.2.2 AI-201.8743.12.41.6953283
Xcode: 13.0/13A233 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_292 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.0 => 0.66.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

10

@Janet We haven’t been able to replicate this however we notice that you are running on 1.6.0 if you update to 1.7.0 do you see any improvement?

11

Also there was an issue for flutter IAP plugin related to targeting certain simulator builds on an M1 mac. We are wondering if aspects of it are still related, like excluding targeting arm64 simulator?

12

yes its only related to arm64 simulator, I’ll try to upgrade the SDK and see if that works, Thanks