throw
How reads that existed in 1.11 report a failed fetch (no connection, timeout, expired session, server error).
false(default): they return the same empty result as 1.11 (an empty list, a blank profile, an empty URL) and the failure is only logged. Apps written against 1.11 need no changes.true: they throw AFException, so an empty result always means the member has no data and the app can show an error state with AFException.message and a retry. Recommended for new integrations; it becomes the only behavior in 2.0.
Reads added in 1.12 (locations(), content(), activePerks() and the new methods on older modules) always throw on failure.