Integration and Testing

Authorize.Net API questions and help with your payment integration.

Reply
Highlighted
Member
Posts: 2
Registered: ‎03-11-2021

A couple issues on the In-Person SDK IOS

Hi,

 

We're working on the bbpos device and in-person sdk here. https://github.com/AuthorizeNet/inperson-sdk-ios

 

However, we're facing 2 issues.

1. https://github.com/AuthorizeNet/inperson-sdk-ios/issues/93

This one mentioning the app is crashed once we try to login with username and password. For detail, please check the link.

 

2. Another big issue, the Error is being conflicted with Error in AVFoundation which was posted almost a year ago. Why don't we have anyone take care of these issue? 

https://github.com/AuthorizeNet/inperson-sdk-ios/issues/91

 

Please help us on these issues. We're gonna buy the hundred devices to integrate with all our parners, but we're blocking on this and can't go.

 

Thank you!

Manh

Member
Posts: 2
Registered: ‎03-11-2021

Re: A couple issues on the In-Person SDK IOS

Hi all,

 

We have just made some workaround on these issues and now it's working well for us. However, I still want to say there's a crash bug in the in-person ios sdk. Let's ask your developers fix it. Specifically, here's what I did.

 

For the first one, https://github.com/AuthorizeNet/inperson-sdk-ios/issues/93

We created an extension of the NSNumber and define a function: isEqualToString:(NSString *). Let's tell your developer that NSNumber can't compare to the NSString. 

 

For the second one, right now, there's NO WAY to use the SDK's objects in Swift directly. We built a Wrapper class in ObjC and bridge that class to Swift.

 

Hope this one helps.

Member
Posts: 1
Registered: ‎03-12-2021

Re: A couple issues on the In-Person SDK IOS

Regardless, we in general understand that those extraordinary organizations are expensive, and an impressive part of us can't bear the Syncler FireStick expense of their participation portions.Along these lines, the Syncler APK offers a response for the people who can't pay such a participation portion for hose premium expert communities.

Member
Posts: 2
Registered: ‎05-12-2021

Re: A couple issues on the In-Person SDK IOS

[ Edited ]

This has appeared in the past and it seems not enough care has been taken to avoid the naming collisions, see #24

This is a critical conflict since it conflicts with a Foundation protocol.

Using SDK v4.2, Targeting iOS 12, using Swift 5.

 

cheatengine exiledros savegame

Member
Posts: 2
Registered: ‎05-12-2021

Re: A couple issues on the In-Person SDK IOS

 Version 6.4.0 iOS Messaging SDK

Release Date: May 7, 2021Environmental Requirements

The iOS Mobile Messaging SDK version 6.4.0.787 is supported on iOS versions 12 through 14.

This XCFramework was compiled with Swift version 5.2.4 (swiftlang-1103.0.32.9 clang-1103.0.32.53) which means it will work Swift version 5.2.4 and above.

 

 

XCFramework is supported on CocoaPad versions 1.9.0 and greater.Enhancements

Adding a self awareness process to help SDK recover after discovering a corrupted keychain preventing empty bubbles from being shown on the Conversation Screen.

Adding reporting capabilities for Proactive and IVR Deflection to App Messaging featureBugs fixed

  • Fixed the issue when changing value for maxPreviousConversationToPresent fails to reflect new value
  • Fixed the issue with Video and Voice call invite UI shows square buttons instead of round ones.
  • Fixed the issue with VoiceOver focus interaction will read out:
    • error messages from Structured Content.
    • Structured Content buttons as links.
    • Fixed the issue with background task on LPSocket not ending properly will cause the OS to kill the Host App.
    • Fixed the issue with inconsistent scrolling when showing the Conversation Screen.
    • Fixed the issue with unread message count banners not shown while in the Conversation Screen.
    • Fixed the issue with LPMessagingSDKAgentDetails was being called only once per Conversation.
    • Fixed the issue where SDK will increase memory footprint when repeatedly opening and closing the Conversation Screen.
    • Fixed the issue when failing to access resources from device storage will cause images not to load.New Configurations: inAppReportingEnabled

      Enable or disable sending reporting events for Proactive and IVR Deflection to App Messaging.

      • Type: Bool
      • Default Value: truestructuredContentLoadingImage

        Structured content loading image when images are being fetched/loaded

        • Type: UIImage?
        • Default Value: image named LP_LINK_PREVIEW_LOADER_ICONstructuredContentBrokenImage

          Structured content loading image when images failed to fetched/loaded

          • Type: UIImage?
          • Default Value: image named LP_BROKEN_IMAGE
            Version 6.3.0 iOS Messaging SDK

            Release Date: March 15, 2021Environmental Requirements

            The iOS Mobile Messaging SDK version 6.2.0 is supported on iOS versions 12 through 14.

            This XCFramework was compiled with Swift version 5.2.4 (swiftlang-1103.0.32.9 clang-1103.0.32.53) which means it will work Swift version 5.2.4 and above.

            Hax4you update

             

Member
Posts: 1
Registered: ‎09-19-2021

Re: A couple issues on the In-Person SDK IOS

Free credit card generator will basically take your information and then random credit card generator number for you. Here is what that would entail: The computer creates a credit profile for you out of the information you provide.