Please, refer to the following as general recommendations. If your problem persists, we would appreciate if you send us a sample project for building the plugin that is reproducing the problem when the plugin is added to AppBuilder.
AppBuilder has some requirements and restrictions for custom plugins
which we assume you have already consulted. In brief, they have to be Plugman
compatible. Hopefully, the whole section of the documentation
will be enough comprehensive to help you avoid common problems with custom plugins in AppBuilder.
1. According to the Plugman specs sheet the <framework>
tag is supported.
Could you please verify that when building the plugin the EverliveSDK.framework was added properly into the Link Binary with libraries
section in the build phases of your XCode project? There is a bug report
for Plugman that describes such behaviour.
Also, it would be reasonable to verify:
The path to the framework in XCode is correct.
- From your project targets select Build settings
> Framework search paths
- Make sure that the path matches the actual path to the target framework.
- Clean the project and rebuild it.
The -objC flag in Other Linker Flags section.
The reference to the EverliveSDK.framework. When dragging the EverliveSDK.framework to the Frameworks group of your project:
- (If the EverliveSDK.framework folder was added manually in the project folder) - unselect "Copy items into destination group's folder". Make sure that your target is selected in "Add to targets".
- (If the EverliveSDK.framework folder was not added manually in the project folder) - select "Copy items into destination group's folder".
2. There might be several major reasons for such exception. Please, consult these community threads for addressing the most common cases here and here.
Please, keep us informed with the progress on this issue.
Everlive is now Telerik Backend Services
, and is part of the Telerik Platform
. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar
on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)