Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Application restrictions issues #20

Closed
ain-is opened this issue Dec 5, 2016 · 3 comments
Closed

Application restrictions issues #20

ain-is opened this issue Dec 5, 2016 · 3 comments

Comments

@ain-is
Copy link

ain-is commented Dec 5, 2016

During application restrictions testing I have found several issues in latest 3.0.11 version:

  1. andorid:restrictionType="choice" is not supported. Choice restriction is displayed just as string restriction. Data provided by application using android:entries and android:entryValues are ignored.

  2. If application defines complex restrictions using andorid:restrictionType="bundle_array" with several different settings inside each bundle, then string restrictions are not handled properly. String restrictions inside bundle are displayed as boolean and default values are ignored.

  3. Restrictions are displayed in some random order. Not is order defined by application.

@ghost
Copy link

ghost commented May 17, 2019

There is an update to (2) . Please refer to Issue #86

@mbiebl
Copy link

mbiebl commented Aug 13, 2019

Still an issue with 6.1.2

@jscott1989
Copy link
Collaborator

Closing all outstanding pull requests + issues as we've reworked the app to now build with Bazel. With this change, we should be able to properly accept pull requests going forward so these won't sit around for so long. If this is still relevant please check it with the latest version [Using the Android T SDK] and re-open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants