docusign / docusign-objc-client

The Official DocuSign Objective-C Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.
https://www.docusign.com/devcenter
MIT License
13 stars 14 forks source link

Lack of Documentation for iOS #5

Closed drewpitchford closed 6 years ago

drewpitchford commented 7 years ago

Hi! I'm attempting to integrate docusign into a client app on iOS. The documentation for how to use this library is kind of limited in my opinion. Even the docs on the site are a bit confusing. We want a user to be able to sign within the app (without leaving it). So a couple of questions to begin with: Do we have to have the user provide some sort of authentication creds? Do we have to have native UI for the user to sign the PDF or is a webivew what is needed (UI is done by Docusign)?

Really, a step by step guide on how to integrate this into an iOS app would be appreciated.

dirtydanee commented 7 years ago

+1

dktan commented 6 years ago

As I read through the code, I'm pretty sure that they don't have native UI for the user to sign the PDF. What they give is a url, just like their web api. And their code is buggy and docs are misleading. So, this sdk kinda useless.

mmallis87 commented 6 years ago

@drewpitchford @dirtydanee @dktan I think what you guys are looking for is the iOS native SDK: https://docs.docusign.com/ios_sdk/ That SDK has native UI for signing, is well documented and come with sample apps.

That's been said, this pod lib is an http wrapper around DocuSign API. The API doesn't have a native way of signing. The API supports (in-app) browser signing only (web view, iframe...).

dktan commented 6 years ago

@mmallis87 This is what your website lead me to, and what docusign sales manager told me to look into. They have a lot to fix.

mmallis87 commented 6 years ago

The native SDK is listed in the Developer Center under SDKs: https://www.docusign.com/developer-center/api-overview#sdks

We are aware that the documentation and the information architecture is misleading in the current Dev Center and we are fixing that in the new version that is going to be published in a month from now.

suneelseelam commented 5 years ago

Hi, I am using (https://github.com/docusign/docusign-ios-sdk) from past few years, currently I am getting an old SDK crash. so I thought to change the SDK But in the new SDK (https://github.com/docusign/docusign-objc-client) I have no Idea to integrate new SDK can anyone please share the example code if there to Integrate new SDK. Thanks in Advance.

mmallis87 commented 5 years ago

@suneelseelam You'll find some examples here: https://github.com/docusign/docusign-objc-client/blob/master/test/SdkTests/SdkTestsTests/SdkTestsWithJwtAuth.m

LarryKlugerDS commented 5 years ago

A JWT .NET Core solution code example for the current version of the SDK is available here: https://github.com/docusign/blog-csharp-order-form

In addition, other examples for C# are available (see the repo list) but they are not yet updated to the new version of the SDK. That work is in progress and is expected to be complete by Nov 12, 2018

suneelseelam commented 5 years ago

We are integrating with Salesforce, I have envelope Id with the Help of envelope id, I am opening the DocSign, Is it possible to do in the same way as previous sdk.

[self.testConfig.apiClient configure_jwt_authorization_flow:self.testConfig.integratorKey userId: self.testConfig.userId oauthBasePath:self.testConfig.oauthBasePath privateKeyFilename:self.testConfig.privateKeyFilename expiresIn:self.testConfig.jwtTokenExpiresInSeconds ];

In oauthBasePath, privateKeyFilename, userId tags what should be passed