...
| Guideline | Android app development applicable? | Original Comments | TC Comments | |
|---|---|---|---|---|
| OBJ03-J. Do not mix generic with nongeneric raw types in new code | [Applicable] | Could not I couldn't find a page with this title. Should it go to this page, which This page has the same number? : OBJ03-J. Prevent heap pollution. Do you want me to link to this page? | ||
| FIO08-J. Use an int to capture the return value of methods that read a character or byte | [Applicable] | This page was deleted. We can ask for it to be undeleted. Please advise.>= | ||
| FIO11-J. Do not attempt to read raw binary data as character data | [Applicable] | The link on the left does not work. Please advise. > Do you want to link to this page? STR03-J. Do not convert between strings and bytes without specifying a valid character encoding | ||
| OBJ56-J. Provide sensitive mutable classes with unmodifiable wrappers | Unknown | ? | How should this be categorized? | |
| SEC57-J. Do not let untrusted code misuse privileges of callback methods | Unknown | How should this be categorized? | ||
| IDS00-J. Sanitize untrusted data passed across a trust boundary | The rule uses MS SQL Server as an example to show a database connection. However, on Android, DatabaseHelper from SQLite is used for a database connection. Because Android apps may receive untrusted data via network connections, the rule is applicable. | Which page should this entry link to? |
...