Upgrade older app with plugins added manually

[M&M]

Here is the GUID: b0c04400-7a73-415d-88c7-5fda9380c9c0

The app does not have any code except for the camera plugin. I have also shared the app with support. The app name is "test"

[M&M]

The error message it shows is

Build error

Most likely build error cause:

Please try again.
You can also email us a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a and tell us about this problem

[Serhii Kulibaba]

The problem in your AndroidManifest.xml file. Please look at error from the log file:
preandroid/172285/381058/android/test/AndroidManifest.xml:61:5 Error:
Element uses-feature#android.hardware.camera at AndroidManifest.xml:61:5 duplicated with element declared at AndroidManifest.xml:58:5
/srv/tiggzi/jenkins/workspace/381058-android/172285/381058/android/test/AndroidManifest.xml:0:0 Error:
Validation failed, exiting
FAILED

FAILURE: Build failed with an exception.

• What went wrong:
  Execution failed for task ':processDebugManifest'.
  Manifest merger failed with multiple errors, see logs/pre

[M&M]

Thanks. So what I did was to remove this line from plugin.xml
code
<uses-feature android:name="android&#46;hardware&#46;camera" />
/code

And then APK build was successful. But the plugin does not work! The same plugin (from the same zip file) works 100% fine in v2.3 app. I need this plugin to work because my app needs to capture picture with preview. If you need I can create a v2.3 app with same camera plugin manually and share with you. Please suggest as this is urgent and we need to release app in the app store fast

[Illya Stepanov]

Unfortunately custom plugins are outside the scope of standard Appery.io platform support. You may consider purchasing Advisory Pack to get more in-depth help on this question. Here is more information about it: http://appery.io/services/#Advisory_Pack

[M&M]

hi Illya,

I am not asking for help on anything custom as such. The same 'Cordova Plugin' works fine when I added it manually in v2.3. The same zip file containing the plugin, when I import using the new import feature, it does not work. All I want to know is why something that works 100% fine when added manually does not work when using the import feature and if we don't release the app soon to the app store, we will be having many angry customers. We are under the Pro plan for couple of years now but if we have such difficulties over small issues then we seriously need to rethink about switching to other platforms. I have also asked question using the priority support in my appery login. I have no satisfactory answer there too. Please understand that I am not asking about some custom function in my custom plugin. All I am saying is the plugin works in v2.3 when added manually...and it does now work in v3.0

[Illya Stepanov]

There are many reason why a custom Cordova plugin might not work. When you upgrade from app library version 2.3 to version 3.0 you are also upgrading from Cordova 3.7 to Cordova 4.0. This might be the reason the plugin doesn't work. We would love to help you more. Please consider purchasing the Advisory Pack support: http://appery.io/services. With this support package, we will help you debug the custom Cordova plugin or any other parts of your app. We can also help you with any other integrations or custom app code.

[M&M]

Well, as of now we only have 1 app under active development which we plan to give away for free. And also the subscription we have is a pro account, so it it not economical for us the pay for the advisory pack when all we need is to be able to get the plugin to work. I have checked with the author and there are installations on Cordova 4.0 which works perfectly fine. As a matter of my my v2.3 works very well. If I could know the location of the folder or the files into which the plugins get copied, I can see if I can change some settings to make it work. I hope you understand....what I mean is can I have some idea as to where the plugin files go to, when it is added to a project? If I know this I can see if I can troubleshoot this myself and this will also help people who have similar issues. Now it is like a complete sandbox

[M&M]

I guess I won't get a satisfactory reply to my above question/problem

[Illya Stepanov]

We are clarifying this with our development team, thank you for your patience.