Hey!
after doing something like \.gradlew archive,Debug,... package with a Debug build, the app crashes right on launch. I debugged that a bit and the error message was telling me AppName.debug.dylib not valid for use in process: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed..
Turns out, it seems like Xcode 16 introduced a new build setting, called ENABLE_DEBUG_DYLIB that, when set to YES, produces a file named AppName.debug.dylib, that is loaded by the main binary on launch. That dylib apparently is not signed properly (and I am not sure if it should be there in the first place) as its mainly used that things like previews work properly.
I worked around that by providing ENABLE_DEBUG_DYLIB=NO as additional build parameter, but wonder if that should maybe be done by the gxp?
Happy to do a PR on that once clarified how to proceed with that.
Hey!
after doing something like
\.gradlew archive,Debug,... packagewith a Debug build, the app crashes right on launch. I debugged that a bit and the error message was telling meAppName.debug.dylib not valid for use in process: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed..Turns out, it seems like Xcode 16 introduced a new build setting, called
ENABLE_DEBUG_DYLIBthat, when set to YES, produces a file namedAppName.debug.dylib, that is loaded by the main binary on launch. That dylib apparently is not signed properly (and I am not sure if it should be there in the first place) as its mainly used that things like previews work properly.I worked around that by providing
ENABLE_DEBUG_DYLIB=NOas additional build parameter, but wonder if that should maybe be done by the gxp?Happy to do a PR on that once clarified how to proceed with that.