Page MenuHome

macOS code signed release errors with Python ctypes
Closed, ResolvedPublic

Description

System Information
Operating system: macOS 10.14.5
Graphics card: n/a

Blender Version
Broken: Blender 2.80 rc1
Worked: buildbot, any unsigned build

Short description of error
Using ctypes in add-ons is failing to work in the release candidate build that is code signed and notarized.

Exact steps for others to reproduce the error
Run import ctypes in the console editor, a MemoryError will be thrown.

Event Timeline

The latest build should work now, it's identical to the previous one except for different code signing:
https://download.blender.org/release/Blender2.80/blender-2.80rc1-macOS.dmg

Hi @Brecht Van Lommel (brecht) . I'm still seeing an issue with that link you sent.

Here's the error

types.CDLL(str(rpr_lib_path))
  File "/Applications/Blender.app/Contents/Resources/2.80/python/lib/python3.7/ctypes/__init__.py", line 356, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: dlopen(/Users/bsavery/Library/Application Support/Blender/2.80/scripts/addons/rprblender/libRadeonProRender64.dylib, 6): no suitable image found.  Did find:
	/Users/bsavery/Library/Application Support/Blender/2.80/scripts/addons/rprblender/libRadeonProRender64.dylib: code signature in (/Users/bsavery/Library/Application Support/Blender/2.80/scripts/addons/rprblender/libRadeonProRender64.dylib) not valid for use in process using Library Validation: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)

We don't sign the dylibs that come with RPR.

No time to test today to replace the official build, but this one should work in theory:
https://download.blender.org/ftp/brecht/builds/blender-2.80rc1-macOS.dmg

Official build updated now.