Troubleshooting and FAQs
This section includes troubleshooting techniques and frequently asked questions (FAQs) about Silent Network Authentication in RiskOS™.
Common errors
| Issue | Explanation | Suggested fix |
|---|---|---|
| Common integration errors | Missing carrier support, network/connectivity problems, incorrect SDK key, or device lacking cellular data. | Use the SDK’s error callbacks and error codes for troubleshooting. Verify carrier support and network access. |
| Mobile SDK permissions and initialization | For Android, the SDK requires the CHANGE_NETWORK_STATE permission. The SDK does not prompt end users for permissions; the host app must handle them. | Add CHANGE_NETWORK_STATE in the Android manifest. Ensure the correct SDK key is used during initialization. |
General product behavior
How long does Silent Network Authentication take?
SNA generally completes within 1 second but may take up to 4 seconds in some scenarios.
Developers often display a “validation in progress” screen while waiting.
Which carriers and devices are supported? Is SNA available outside the US?
SNA is currently supported for U.S. carriers: T-Mobile, Verizon, and AT&T.
International availability and additional carriers may require configuration — contact the Solutions Consultant team for details.
What happens if the device is on Wi-Fi or doesn’t have an active SIM?
The SDK will attempt to switch from Wi-Fi to cellular during SNA.
If cellular data or an active SIM isn’t present, authentication cannot be completed.
The SDK reports these outcomes for RiskOS workflow decisioning.
Is SNA integration available for all Socure Digital Intelligence SDKs?
Yes. SNA is available through Socure’s Digital Intelligence SDKs (iOS, Android, React Native) and can be orchestrated within RiskOS flows.
Note: SNA is not available for the Digital Intelligence Web SDK.
Updated 4 months ago