-
Notifications
You must be signed in to change notification settings - Fork 508
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
Not able to add multiple comma separated values against one metadata name in Android Manifest #1764
Comments
Lists can be provided in either of two formats. The other format should work. (I have looked at the code but haven't tested.) Please try this:
(If it works, don't forget to close the issue.) |
Thanks @Julian-O but unfortunately the above method doesn't work and when I use that in the spec then the rest of the spec is not parsed fully after this line. This creates a new build without all the arguments given in the spec after I use the suggested method. |
@Samael-TLB: Can you please submit your Buildozer.spec (after removing anything that is commercially sensitive) so we can see it that is a bug in the parser that needs fixing? |
Surely, below is what I'm using currently:
|
I wrote a quick unit-test using the file above (with the second format uncommented) and confirmed that it (unexpectedly) parsed the rest of the file as meta-data options, as claimed. |
Okay, I understand better now. There are two formats for lists.
Assuming As pointed out, this doesn't work well when commas are part of the values. The other format is:
This works better with commas and equal signs. In the example provided above (when the second option is uncommented), everything below This means, for example:
is not parsed as its own token, but is (correctly, but unexpectedly) parsed as an item of To get it to work properly, move the I have convinced myself that the parser is behaving as designed and it is possible to represent values with commas. The next question is: Is that enough and we can close the issue? Or do we need to improve the documentation? Or do we need to improve the parsing? |
Thank you @Julian-O for triaging the issue. I'm confirming that the specified method of denoting either before the app section or buildozer section works. To be noted we can not use quotations in denoting the values that is:
The above doesn't work as the value is put inside quotations in the android manifest.
I think we need to improve the docs to make this alternative usage more evident and also should improve the parsing in the normal syntax too. |
Is this still a problem? |
Versions
Description
In buildozer, we have the meta-data field, which takes comma separated meta data in the form of key=value.
But there is a certain limitation, a few meta data keys might take multiple comma separated values like MLKit meta data, etc. In the present format we are not able to do that as the separation of multiple key values is being taken as a comma no matter where the key occurs, if we try to provide the same key multiple times, then they are not merged into one and written as separate meta data tags having same name which breaks the build.
We need a way around this limitation, which shall be an easy fix through regex, etc.
buildozer.spec
Command:
Spec file:
The text was updated successfully, but these errors were encountered: