Receive URL / content from phone browser / other app

[Evgene Karachevtsev]

Hello Peter,

BarCodeScanner plugin is added automatically. You may remove it if you don't need it

[maurice7228714]

Hello Evgene, and thank you for your instruction. I have followed your guidance on installing the webintent plugin and can now share a URL to my appery app. I'm having unexpected results, however.

When sharing a webpage with the app, it only displays the name of the page and a QR code.

The instructions you posted, included a block of javascript to be run on the 'deviceready' event:
Inline image 1

In my testing, I added a couple of alerts to this code in order to find out if it was being called and what effect it would have on my results.
Inline image 2

I'm seeing the 'deviceready' alert message when I start the app from the icon, but I don't see the 'no inbound link' alert message (which is what I'm expecting to see).

When sharing a URL to the app, I'm expecting to see both the 'deviceready' and the URL alert messages but I see nether. I still only see the QR code and the name of the webpage.

Appery is the tool I've been looking for to get into app development and I recently upgraded my account in order to make better use of the platform. I'm also glad that your support is so timely in replying with help.

[Evgene Karachevtsev]

Hello,

1) Could you please clarify, did the plugin connected normally? Are there any errors in the console when you run this code?
Please make this alert on the device ready event
prealert(window.plugins.webintent);/pre
What will be the result?
2) Please try to hang this code not on the device ready event, but on Resume event

[maurice7228714]

Hello Evgene.
Thanks for the reply. To perform the test you suggested, I created a brand new blank app and went through the steps you described to add the webintent plugin.

Then I performed the tests you suggested in your previous comment:

1) hanging the js code [alert(window.plugins.webintent);] on the Resume event produced no alert notification

2) hanging the js code on the DeviceReady event produced no alert.

I am taking the route of reaching out to the phonegap community for guidance on how to disable / remove the barcodereader plugin. Please feel free to suggest solutions and I will try them out.

Thanks.

[maurice7228714]

Can Appery.io be used to build apps that can respond to android intents? or is that beyond the capabilities of the platform?

[Evgene Karachevtsev]

Hello!

1) Appery.io applications work well with webintent. But the fact that you have no alerts means you do not have properly connected the plug-in. Please check it again all, look at the logs http://developer.android.com/tools/he...
or so
https://play.google.com/store/search?...

2) In your Android application, you can delete any plugin if you want directly in the Builder. To do this, you can make changes to any files on the source tab in the ANDROID folder (for example you can remove the barcode scanner from files pom.xml (root project) and from the default.properties of the project)
But you do it on your own risk.
For iOS you can remove the plug-ins only via xCode

[maurice7228714]

OK. So, it's good to know there is a log system. This seems to be an android feature and not directly related to the Appery environment. I'll look further into this but this pom.xml file seems to be a more likely avenue to finding an immediate solution.

First off, your instructions for installing a third party plugin made no mention of pom.xml so I made no changes there.

Where is the structure and syntax of pom.xml documented on the Appery system?

[Yurii Orishchuk]

Hi Maurice,

Unfortunatly we don't have such documentation.

Hope following link could help you:

http://kenfogel.ulitzer.com/node/2912905

Regards.

[maurice7228714]

Hello Yurii.
I'm beginning to get frustrated by the limitations of the appery platform. Too many times the Appery staff's suggestions have been to figure it out myself and to have 'good luck' doing it. This isn't why I became a customer.

[Alena Prykhodko]

Dear Maurice,

Sorry to hear this. We are working to improve documentation, but unfortunately, we cannot create documentation for every specific case.