Calling Builder.sign_file results in undefined symbol: c2pa_builder_sign_file

[rokclimb15]

c2pa_signer_create
[ERROR] AttributeError: /usr/local/lib/python3.12/site-packages/c2pa/libs/libc2pa_c.so: undefined symbol: c2pa_builder_sign_file
Traceback (most recent call last):
  File "/index.py", line 96, in lambda_handler
    signed_manifest_bytes = c2pa_lib.write(file_path, manifest_payload, public_key, sign)
  File "/c2pa_lib.py", line 17, in write
    signed_bytes = builder.sign_file(filename, tmp_output, signer)
  File "/usr/local/lib/python3.12/site-packages/c2pa/c2pa.py", line 1812, in sign_file
    result = _lib.c2pa_builder_sign_file(
  File "/usr/local/lib/python3.12/ctypes/__init__.py", line 392, in __getattr__
    func = self.__getitem__(name)
  File "/usr/local/lib/python3.12/ctypes/__init__.py", line 397, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))

[tmathern]

Can you share additional information to help investigate?

Like: Operating system (OS), OS Version, CPU architecture.
Also, are you running in DOcker or in any cloud architecture?

[rokclimb15]

This is Debian buster, ARM64. It's running on AWS Lambda via a Docker image. I suspect this will reproduce on any Linux architecture however, it looks like a missing exported symbol from the Rust C bindings which are embedded in this version.

…

On Thu, Jun 19, 2025 at 2:44 PM tmathern ***@***.***> wrote: *tmathern* left a comment (contentauth/c2pa-python#122) <#122 (comment)> Can you share additional information to help investigate? Like: Operating system (OS), OS Version, CPU architecture. Also, are you running in DOcker or in any cloud architecture? — Reply to this email directly, view it on GitHub <#122 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEOMZ7CONMFXGLDAIVHMAD3EMAHHAVCNFSM6AAAAAB7UFPWGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBYHA4DKNBSGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[tmathern]

As an aside, I don't think it reproduces on all architectures, because the tests on Ubuntu and Ubuntu ARM for the publish workflows pass, eg #121.

There was a v0.10.0 that had a similar issue. Are you on v0.11.0? That one added more ARM support.

[rokclimb15]

Yes, I am using v0.11.0

…

On Thu, Jun 19, 2025 at 4:06 PM tmathern ***@***.***> wrote: *tmathern* left a comment (contentauth/c2pa-python#122) <#122 (comment)> As an aside, I don't think it reproduces on all architectures, because the tests on Ubuntu and Ubuntu ARM for the publish workflows pass, eg #121 <#121>. There was a v0.10.0 that had a similar issue. Are you on v0.11.0? That one added more ARM support. — Reply to this email directly, view it on GitHub <#122 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEOMZ7TU2SYR6RFGCVBUHD3EMJ4RAVCNFSM6AAAAAB7UFPWGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBZGA3DGMBWHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[rokclimb15]

The unit tests are passing on Ubuntu ARM64, but they don't seem to cover Builder.sign_file. They only cover the deprecated c2pa.sign_file function. https://github.com/contentauth/c2pa-python/blob/main/tests/test_unit_tests.py#L911 I think that untested code path is where the issue is

…

On Thu, Jun 19, 2025 at 4:06 PM Brian Morton ***@***.***> wrote: Yes, I am using v0.11.0 On Thu, Jun 19, 2025 at 4:06 PM tmathern ***@***.***> wrote: > *tmathern* left a comment (contentauth/c2pa-python#122) > <#122 (comment)> > > As an aside, I don't think it reproduces on all architectures, because > the tests on Ubuntu and Ubuntu ARM for the publish workflows pass, eg > #121 <#121>. > > There was a v0.10.0 that had a similar issue. Are you on v0.11.0? That > one added more ARM support. > > — > Reply to this email directly, view it on GitHub > <#122 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAEOMZ7TU2SYR6RFGCVBUHD3EMJ4RAVCNFSM6AAAAAB7UFPWGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBZGA3DGMBWHE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[tmathern]

I saw, just created a PR with a fix.
Until there is a bugfix release, you could also switch to use the streaming API.

Update: for reference, using streams is in the lines of:

def test_streams_sign(self):
        with open(self.testPath, "rb") as file:
            builder = Builder(self.manifestDefinition)
            output = io.BytesIO(bytearray())
            builder.sign(self.signer, "image/jpeg", file, output)
            output.seek(0)
            reader = Reader("image/jpeg", output)
            json_data = reader.json()
            self.assertIn("Python Test", json_data)
            self.assertNotIn("validation_status", json_data)
            output.close()

(builder.sign(self.signer, "image/jpeg", file, output) function)

[rokclimb15]

Thanks, no rush on our end, we're good on 0.6.0 for now.

…

On Thu, Jun 19, 2025 at 4:21 PM tmathern ***@***.***> wrote: *tmathern* left a comment (contentauth/c2pa-python#122) <#122 (comment)> I saw, just created a PR with a fix. Until there is a bugfix release, you could also switch to use the streaming API. — Reply to this email directly, view it on GitHub <#122 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEOMZYQESYMX2EGTBUX3UD3EMLU7AVCNFSM6AAAAAB7UFPWGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBZGA4DINZUGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[tmathern]

A release v0.11.1 fixes that (https://github.com/contentauth/c2pa-python/releases/tag/v0.11.1).
In the future we'll also update the underlying bindings for better performance.