Fix CSV parsing error by stripping UTF-8 BOM before parsing #3682
+17
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix: Remove UTF-8 BOM Before CSV Parsing
This PR fixes an issue where CSV files containing a UTF-8 BOM (
EF BB BF) fail when used with the list from CSV table and list from CSV row blocks.Certain editors automatically insert a BOM at the start of text files. When passed into
fromCsvTableorfromCsvRow, the BOM becomes the first character of the first cell, causing the CSV parser to throw an error.✅ What This PR Does
\uFEFF) in the input CSV stringCsvParser🔧 Modified Methods
fromCsvTablefromCsvRow📌 Why This Matters
This improves App Inventor’s robustness, especially when users load CSV files created in Excel, Google Sheets, or text editors that include a BOM by default.
🔗 Related Issue
Fixes Issue #948: “Cannot parse list as CSV table error with BOM marker”