mblanchard's account

Here's the screenshot :

Thank you, We hope the next release will come out soon !

Hi, When I parse the PDF with PDFHelper.parsePDFToObjects(atPath: path), I only receive 4 objects which are my 4 signatures zones. However, I have a lot of textfields, about 50. I parse strings with Apple's PDFKit. However, on save, I think I lose objects recognizable by the PDFParser.

Thank you for the detailed reply, Our use case is this one : We want to map the PDF, (not hard coding directly in the PDF) with our data. We have about 100 TextFields that needs to be mapped. I tried using the PDFHelper that comes with the SDK however it doesn't recognize the ID attached to a specific TextField. You can see a screenshot of the dictionary that I receive after parsing the PDF with PDFHelper.parsePDF(). So, we used Apple PDFKit to map our data with the corresponding textfields, and this is working fine. When using ESignLive SDK, we don't want that textFields to be editable. In fact, we could flatten the pdf before signature but we're losing also the signature zones when doing this. The best case scenario would be that we map our textfields without flattening the pdf and that it opens up in the SDK in a read-only mode, except for the signature zones. Hope it is more clear now

For point 1, the steps to reproduce the error is this : 1. Start a transaction from PDF while having internet connection 2. Close transaction 3. Lose connection (or go on Airplane mode) 4. Try to start another transaction from PDF without connection Starting a transaction implies that we call this method:

eSignLive.dashboard().login()

. But the dictionary callback gives us this error :

Error Domain=Server Error Code=500 "(null)"

Is it because we call login() each time we want to start another transaction ?