DatePicker "SigningDate" fails on selecting date

WinForms application. OneSpan web page several pages has DatePicker at the second page

Hi LCG,

Thanks for your post! According to your description, it sounds like when your code defines the datepicker field, it didn't specify the date format (it's one of the field validation). If you are developing with .NET SDK, check below sample code:

            FieldBuilder datepicker = FieldBuilder.Datepicker()
                    .WithValidation(FieldValidatorBuilder.Regex("YYYY-MM-dd").Required().WithErrorMessage("Please select a current or past date!"))
                    .OnPage(0)
                    .AtPosition(300, 300)
                    .WithSize(200, 55);

            DocumentPackage package = PackageBuilder
                    .NewPackageNamed("Sample Package")
                    .WithSigner(SignerBuilder.NewSignerWithEmail("[email protected]").WithFirstName("John").WithLastName("Smith"))
                    .WithDocument(DocumentBuilder.NewDocumentNamed("Document1").FromFile("your_file_path").WithId("DOCUMENT1")
                            .WithSignature(SignatureBuilder.SignatureFor("[email protected]")
                                    .OnPage(0)
                                    .AtPosition(100, 100)
                                    .WithSize(200, 55)
                                    .WithField(datepicker)
                                    ))
                    .WithStatus(DocumentPackageStatus.SENT)
                    .Build();
            PackageId packageId = ossClient.CreatePackageOneStep(package);
            Debug.WriteLine(packageId);

Duo

Hi, Thank you for your reply.

We are not defining datepicker from the code. We are loading web page into web browser component Microsoft.WebView2.

https://apps.esignlive.com//auth?signerAuthenticationToken=[tokenExpired]&target=[someTarget]

Web page has an issue with loading js script or js package

Hi LCG,

I understood that you were experiencing the JS error when loading the Signing Ceremony in a web page, however, the issue was caused when the package first got created. Therefore, it could worth a check for that part of code.

Duo

Try, let me check