We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I encountered an error in the receiver_message_layout.xml file related to the XML declaration. The specific issue is as follows:
receiver_message_layout.xml
Error Message:
lineNumber: 1; columnNumber: 36; White space is required before the encoding pseudo attribute in the XML declaration.
The error is caused by a missing whitespace before the encoding attribute in the XML declaration. The current declaration is:
encoding
<?xml version="1.0"encoding="utf-8"?>
It should be corrected to:
<?xml version="1.0" encoding="utf-8"?>
I have corrected the XML declaration by adding the required whitespace:
This fix resolves the issue and adheres to proper XML formatting.
@Vishwajith-Shettigar please assign this to me under gssoc-ext and hacktoberfest.
The text was updated successfully, but these errors were encountered:
Merge pull request #144 from Saumy1905/missing-whitespace/receiver_me…
b578f7d
…ssage_layout_xml missing whitespace error resolved in the receiver_message_layout.xml (#142)
Saumy1905
Successfully merging a pull request may close this issue.
I encountered an error in the
receiver_message_layout.xml
file related to the XML declaration. The specific issue is as follows:Error Message:
Resolution:
The error is caused by a missing whitespace before the
encoding
attribute in the XML declaration. The current declaration is:It should be corrected to:
Suggested Fix:
I have corrected the XML declaration by adding the required whitespace:
This fix resolves the issue and adheres to proper XML formatting.
@Vishwajith-Shettigar please assign this to me under gssoc-ext and hacktoberfest.
The text was updated successfully, but these errors were encountered: