@Jon Ann, would you mind taking a look at this and letting us know what you recommend in terms of a more obvious string?

@Ben, can you clarify whether we know that the error occurred because no network was available vs. another carrier's network is available, but roaming is disabled? This may inform the string we propose.

@jesse, is it impt for managed user to know that admin may have disabled , or is it enough info to just say that roaming isn't available?

It's not critical, since managed users will see the building icon (and a locked toggle) in the mobile network panel when a roaming policy is in place.

String for review:


<title>
 Couldn’t connect to the internet

<error text>

Either there’s no network available, or your phone isn’t set up for roaming

<buttons>
Cancel
Try again

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.