Spire.PDF for Android: Encryption of PDF/A bug

[RicoScheller]

We have an application that digitally fills out PDFs.
This works like the following:
- Create PDF/A with text fields. Give them unique field names.
- Read PDF/A and insert text into the text fields. Fields are identified by their unique name, so we know where to insert what.
- Once everything is done, protect it against changes by encrypting it.

The problem now is, that encryption in combination with PDF/A changes the field names and thus we can no longer "find" the text fields afterwards.
The following picture shows from left to right:
- Normal file is ok.
- Encrypted file is ok.
- PDF/A file is ok.
- Encrypted PDF/A changes the field names, making the PDFs no longer work with our application.

GarbledFieldNames.png

This does not happen in Spire.PDF for .Net v11.3.0.
So, this behavior in Spire.PDF for Android via Java v10.4.0 has to be a bug.

I've attached a test project.
Can you please check with the developers if they could provide a quick hotfix for that?

[Tommy.Tang]

Hello,

Thank you for providing detailed information. I encountered some issues during testing and will investigate and provide you with feedback as soon as possible.

Sincerely,
Tommy
E-iceblue support team

[Tommy.Tang]

Hello RicoScheller,

I truly apologize for the long wait. Your issue has been logged into our bug tracking system with the ticket SPIREPDF-7550. Our development team will further investigate and fix it. Once there is any progress, we will inform you in time.

Sincerely,
Tommy
E-iceblue support team

[RicoScheller]

Thank you for your update.

However, you telling me that the issue has been logged unfortunately doesn't tell me when I can expect a new version with the fix.
Last time I waited half a year for a new Android version.
It seems like you don't prioritize Android at all.

So I would feel much better if you could provide a rough time estimate.
Because I need to decide if we need to try to roll back to a previous version for our release or if we could wait for a fix!

[Tommy.Tang]

Hello,

I am very sorry for the poor experience caused by the previous repair. We fully understand your concerns, please rest assured that we have marked your issue as a high priority and are actively analyzing and identifying the root cause.
Sorry, we are currently unable to provide an exact repair time as our development team is still investigating the root cause of the issue. I will update you on the latest progress of the issue next week, is that okay? Thank you again for your understanding and patience.

Sincerely,
Tommy
E-iceblue support team

[Nina.Tang]

Hi,

Your issue has been fixed and the changes are now in the testing phase. We expect to release the official version next month. If your situation is urgent, we can also prioritize the compilation of a temporary version for you. Please let us know if you would like this option. We look forward to your feedback.

Sincerely,
Nina
E-iceblue support team

[RicoScheller]

Thank you for the update and the expected release timeframe.

If it's not too much work, a beta version would be nice, then I could test it as well and already provide feedback.

[Nina.Tang]

Hi,

Okay, we will try to provide you with a temporary version within this week.

Sincerely,
Nina
E-iceblue support team

[Nina.Tang]

Hi，

The test team has built a new version and is currently in the final testing phase. We will provide it to you as soon as the testing is completed and no issues are found. Please spare us a little more time. Thanks for your understanding.

Sincerely,
Nina
E-iceblue support team

[Nina.Tang]

Hi，

Thanks for your patient waiting.
The temporary version is available, please download it from here.

Sincerely,
Nina
E-iceblue support team

[RicoScheller]

Thanks for the temporary version.

I can confirm that this now works as expected in my test setup as well as in our application.

I can't seems to apply my license anymore, because the com.spire.license namespace only contains a Blacklist.class and no LicenseProvider.
But I guess this was done on purpose so that we don't accidentally use the beta version in production?

[Nina.Tang]

Hi,

Thanks for your feedback.
In the new version, we have upgraded the licensing mechanism, and the namespace for the license-related classes has been updated.
Please use the following new API:

Code: Select all

com.spire.pdf.license.LicenseProvider.setLicenseKey("your license key");

instead of the old one:

Code: Select all

com.spire.license.LicenseProvider.setLicenseKey("your license key");

Sincerely,
Nina
E-iceblue support team

[RicoScheller]

Unfortunately, there is no com.spire.pdf.license namespace in the jar that you've linked to:

No_license_in_pdf.png

License_package_missing.png

com.spire.license exists, but only contains a Blacklist class and no LicenseProvider:

No_licenseProvider_in_license.png

[Nina.Tang]

Hi，

Thanks for your feedback.
I just confirmed that the version provided to you was a Beta version, intended solely for functional verification and not taking into account your actual License environment. Our testing team is currently compiling a new temporary version, which will be provided to you as soon as possible. We apologize for any inconvenience caused.

Sincerely,
Nina
E-iceblue support team

[Nina.Tang]

Hi，

Thanks for your patient waiting.
The temporary version is available, I have verified that there are no issues with the functionality and application authorization method. Please use the following code to apply the license key:

Code: Select all

com.spire.license.LicenseProvider.setLicenseKey("your license key");

Sincerely,
Nina
E-iceblue support team