Log in to AnswerLog in to Follow
Ricardo Ferreira
661Views
12Comments
Solved
How do I include a permission in the AndroidManifest.xml
Question

How do I include a permission below (Android example) in the settings (AndroidManifest.xml) of an application created with an OutStsems platform?

<activity android:name=".MyScreen">

         <intent-filter>

                  <category android:name="android.intent.category.BROWSABLE"></category>

         </intent-filter>

</activity>


Thanks,

Ricardo Ferreira

0
0
on 2019-02-27

João Santos wrote:

You can accomplish this by changing the Extensibility Configurations definition of the front-end module.


Check this link: https://success.outsystems.com/Documentation/11/Delivering_Mobile_Apps/Customize_Your_Mobile_App/Extensibility_Configurations_JSON_Schema


And also here: https://cordova.apache.org/docs/en/latest/guide/platforms/android/plugin.html


Thanks João


I noticed that the outsystems build is already included in the manifest: 

https://success.outsystems.com/Documentation/Development_FAQs/How_to_Define_Mobile_App_Deep_Links


0
0
on 2019-02-28

Ricardo Ferreira wrote:

João Santos wrote:

You can accomplish this by changing the Extensibility Configurations definition of the front-end module.


Check this link: https://success.outsystems.com/Documentation/11/Delivering_Mobile_Apps/Customize_Your_Mobile_App/Extensibility_Configurations_JSON_Schema


And also here: https://cordova.apache.org/docs/en/latest/guide/platforms/android/plugin.html


Thanks João


I noticed that the outsystems build is already included in the manifest: 

https://success.outsystems.com/Documentation/Development_FAQs/How_to_Define_Mobile_App_Deep_Links


Is there any other thing you want to understand?


0
0
on 2019-03-01

João Santos wrote:

You can accomplish this by changing the Extensibility Configurations definition of the front-end module.


Check this link: https://success.outsystems.com/Documentation/11/Delivering_Mobile_Apps/Customize_Your_Mobile_App/Extensibility_Configurations_JSON_Schema


And also here: https://cordova.apache.org/docs/en/latest/guide/platforms/android/plugin.html



Hi 

I want add this line to manifest file how i can add this? 

<uses-permission
    android:name="android.permission.READ_CALL_LOG"
    tools:node="remove" />
0
0
on 2020-04-30

Swapnil Shinde wrote:

João Santos wrote:

You can accomplish this by changing the Extensibility Configurations definition of the front-end module.


Check this link: https://success.outsystems.com/Documentation/11/Delivering_Mobile_Apps/Customize_Your_Mobile_App/Extensibility_Configurations_JSON_Schema


And also here: https://cordova.apache.org/docs/en/latest/guide/platforms/android/plugin.html



Hi 

I want add this line to manifest file how i can add this? 

<uses-permission
    android:name="android.permission.READ_CALL_LOG"
    tools:node="remove" />

Have you checked this plugin: https://www.outsystems.com/forge/component-overview/2040/android-permissions-plugin ?


0
0
on 2020-04-30

Hi João Santos,

I checkd and used this plugin in my project but my requirement is diiferent.

in my project there is an another plugin name finbox(https://github.com/finbox-in/cordova-plugin-risk-manager)

in that they use some permission in there manifest file you can check in below document

 https://docs.finbox.in/device-connect/cordova.html#handle-permissions

and application manifest file set this permission after generating application and because of this google not approve my application to published on play store.

to resolve this issue they provide this solution, To remove the unused permissions,  add a remove rule to that permission as shown below

<uses-permission
    android:name="android.permission.READ_CALL_LOG"
    tools:node="remove" />
0
0
on 2020-05-01

Swapnil Shinde wrote:

Hi João Santos,

I checkd and used this plugin in my project but my requirement is diiferent.

in my project there is an another plugin name finbox(https://github.com/finbox-in/cordova-plugin-risk-manager)

in that they use some permission in there manifest file you can check in below document

 https://docs.finbox.in/device-connect/cordova.html#handle-permissions

and application manifest file set this permission after generating application and because of this google not approve my application to published on play store.

to resolve this issue they provide this solution, To remove the unused permissions,  add a remove rule to that permission as shown below

<uses-permission
    android:name="android.permission.READ_CALL_LOG"
    tools:node="remove" />

Hello, I've been doing some research and I didn't find anything like that in Outsystems. I would say, that your best option is to customize the Android Permissions plugin (https://www.outsystems.com/forge/component-overview/2040/android-permissions-plugin). You can make a fork of the code that is on github (https://github.com/kelter-antunes/cordova-plugin-android-permission)

0
0
on 2020-05-07

Hi,

Please suggest some solution.

0
0
on 2020-05-07

Any update on this?

We are as well stuck with a deploy to store. Non of our applications need CAMERA but still it's mentioned in the apk.
Therefor we want to use the above code to remove this permission.

0
0
on 19th Jan
Pedro Neto
Champion

Most probably your application is using a plugin that is requiring that plugin in the plugin.xml file.

What Outsystems plugin are you using?

0
0
on 18th Feb

Replying to Pedro Neto's comment on 18 Feb 2021 08:15:37

We have checked the plugins but not of them seem to really need it. But it still is requested, therefor we wanted to overwrite it in the finale build. 

Plugins: ardoJSON, Common Plugin, Firebase Mobile, FirebaseAPI, Google re CAPCHA react, Markdown-lt, Multilanguage, OutSystems UI

0
0
on 18th Feb
Pedro Neto
Champion

Replying to Dieter Vennekens' comment on 18 Feb 2021 08:22:06

If you are sure that permission is not needed on those components, you can go into the plugin.xml of cordova plugin, look for android.permission.CAMERA  and delete that tag.

0
0
on 18th Feb
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.