-
Notifications
You must be signed in to change notification settings - Fork 506
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
SAXparseException when running buildozer #1717
Labels
Comments
Remove the quotes from the |
Thank you for this advice! this solves the error! |
👋 @averagenetworkscienceenjoyer, we use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. Please use our support channels to get help with the project. |
Hello, I would like to know more about this.
El El jue, oct 12, 2023 a la(s) 2:05 p.m., github-actions[bot] <
***@***.***> escribió:
… 👋 @averagenetworkscienceenjoyer
<https://github.com/averagenetworkscienceenjoyer>, we use the issue
tracker exclusively for bug reports and feature requests. However, this
issue appears to be a support request. Please use our support channels
<https://github.com/kivy/buildozer#support> to get help with the project.
Let us know if this comment was made in error, and we'll be happy to
reopen the issu
—
Reply to this email directly, view it on GitHub
<#1717 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANYYRUD7TOXANDGR7ZTNUDTX7AWN3AVCNFSM6AAAAAA54DYHHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRQGEYTKMJQGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Versions
Description
when I run the command below it configures most of the files and then gives this parse exception error. I think it's an issue with gradlew but I don't know how I'm supposed to fix it.
I am using buildozer from wsl (not from android studio), so I have no androidmanifest.xml file to edit.
buildozer.spec
Command:
Spec file:
Logs
The text was updated successfully, but these errors were encountered: