Open fralu98 opened 4 years ago
Hello,
Yes, we are aware of this issue. The manifest.json file is located at the first level of the folder. However, the manifest.json file must be located in the Resources folder as recommended by Apple.
We are working towards a version of the plugin that is more compatible with v18 that will hopefully be available in the next few months. Until then, the source code is provided and you can make changes as you like.
Orchard Software
Hello @OrchardSoftware ,
We are aware of that problem and did try that out aswell. We could not sign the new application with that changed file path of the manifest.json either. Is there maybe another way to solve the problem of code signing or shall we wait for the new version of the plugin?
Thank you very much anyway!
There is not another way that we are aware of.
We are a Windows only shop so this isn't really something we will be investigating. The updated plugin that is coming will be built with a new SDK provided by 4D which we are assuming, hopefully correctly, will fix this issue. We are currently working on this so hopefully it'll be ready before too long.
Okay, there is not another way, I see!
I would love to get an information asap, when the new version of the updated plugin will be released. I hope we can solve our code signing problem with the new version. I will inform you when there is a new version of it, after I could test the code signature with it. Thank you very much for your time!
Greetings!
I'm having a problem on macOS Catalina 10.15.7 with the 4D Version 18 R4-Release, when I try to build a new application. Without the Win32API I can sign the app and build it without any errors. When I add the Win32API-Plugin it does not work anymore because it cannot be signed. With 4D Version 18 R3-Release, there were no problems adding Win32API.
Is there anybody who has the same problem and can help me solving the problem that I have?
If there are more information you need, I will response asap.