Assembly: Veriplace.Client (in Veriplace.Client.dll) Version: 1.6.0.11143 (1.6.0.0)
Syntax
| C# |
|---|
public bool VerifyCarrierLocatability( string mobileNumber ) |
| Visual Basic (Declaration) |
|---|
Public Function VerifyCarrierLocatability ( _ mobileNumber As String _ ) As Boolean |
| Visual C++ |
|---|
public: bool VerifyCarrierLocatability( String^ mobileNumber ) |
Parameters
- mobileNumber
- Type: System..::.String
the mobile number
Return Value
true if the mobile number is valid and is on a carrier that is supported for this application; false if not
Remarks
If this method returns false, then a user with that mobile number would not be able to grant location permission to your application.
Even if the number does not have a registered Veriplace account, Veriplace can determine whether it is a valid number belonging to a supported carrier. If your application has been launched, it may only be certified for certain carriers and not for others.
If your application is still in development and has not been certified for any carrier, then the only mobile numbers that are allowed are the ones you have designated as test phones on the Veriplace Developer Portal (subject to the user's approval: users of those phones can still choose to opt out of "developer mode", in which case they will be unavailable to your application).
If this method returns true, it does not mean that your application can locate the user; you still need to have the user's permission. To check for an existing permission token, use GetLocationAccessToken(User). To ask for permission interactively in a web application using an OAuth redirect, use RedirectToAuthorization(String, User, Boolean). To ask for permission via an SMS messge, use InvitationAPI.
Exceptions
| Exception | Condition |
|---|---|
| Veriplace.Client..::.BadParameterException | if the mobile number was not in a valid format (see UserDiscoveryParameters for acceptable formats) |
| Veriplace.Client..::.UnexpectedException | if there was an unexpected I/O error or OAuth error |