nativescript-cloud
Used for cloud support in NativeScript CLI
Contents
Public API
This section describes all methods that can be invoked when you have installed the nativescript-cloud
extension and NativeScript CLI is required as library. You must load the installed extensions by calling loadExtensions method. After that you will be able to call methods from nativescript-cloud
extension:
const tns = require("nativescript");
Promise.all(tns.extensibilityService.loadExtensions())
.then(loadedExtensionsData => {
});
NOTE: The extension must be installed before using it. You can do it by calling installExtension method of the CLI:
tns.extensibilityService.installExtension("nativescript-cloud@latest")
.then(extensionData => console.log(`Successfully installed extension ${extensionData.extensionName}.`))
.catch(err => console.log("Failed to install extension."));
Contents
nsCloudBuildService
The nsCloudBuildService
allows build of applications in the cloud. You can call the following methods:
build method
build
method validates passed arguments and tries to build the application in the cloud. In case of successful build, the build result (.apk, .ipa or .zip) is downloaded. The result contains information about the whole build process, path to the downloaded build result and information used to generate a QR code, pointing to the latest build result (in S3).
Definition:
build(projectSettings: INSCloudProjectSettings,
platform: string,
buildConfiguration: string,
accountId: string,
androidBuildData?: IAndroidBuildData,
iOSBuildData?: IIOSBuildData): Promise<IBuildResultData>;
Detailed description of each parameter can be found here.
nsCloudBuildService events
nsCloudBuildService
raises the following events:
buildOutput
buildOutput
event contains parts of the current build output:
interface IBuildLog {
buildId: string;
data: string;
pipe: string;
}
stepChanged
stepChanged
event contains the name of the changed build step and its progress:
interface IBuildStep {
buildId: string;
step: string;
progress: number;
}
Events usage
const tns = require("nativescript");
const fs = require("fs");
const path = require("path");
const packageJsonContent = JSON.parse(fs.readFileSync("./package.json", "utf8").toString());
const projectSettings = {
projectDir: process.cwd(),
projectId: packageJsonContent.nativescript.id,
projectName: path.dirname(process.cwd()),
nativeScriptData: packageJsonContent.nativescript,
bundle: true,
env: {
uglify: true
}
};
const androidReleaseConfigurationData = {
pathToCertificate: "./myCertificate.p12",
certificatePassword: "123456"
};
const platform = "android";
const buildConfiguration = "release";
tns.nsCloudBuildService.on("buildOutput", (data) => {
console.log(data);
});
tns.nsCloudBuildService.on("stepChanged", (data) => {
console.log(data);
});
const accountId = "d0ce3ac0-36c2-427f-8d27-955915ffe189";
tns.nsCloudBuildService
.build(projectSettings, platform, buildConfiguration, accountId, androidReleaseConfigurationData)
.then(buildResult => console.log(buildResult))
.catch(err => console.error(err));
validateBuildProperties
validateBuildProperties
method validates all properties required for specific platform. This includes a check if current application identifier matches the CodeSigning identity for iOS operations, a check if the specified device identifier (in case it is passed) is included in the mobile provision, validation of the password, etc.
Definition:
validateBuildProperties(platform: string,
buildConfiguration: string,
projectId: string,
androidBuildData?: IAndroidBuildData,
iOSBuildData?: IIOSBuildData): Promise<void>;
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
const fs = require("fs");
const path = require("path");
const packageJsonContent = JSON.parse(fs.readFileSync("./package.json", "utf8").toString());
const projectId = packageJsonContent.nativescript.id;
const androidReleaseConfigurationData = {
pathToCertificate: "./myCertificate.p12",
certificatePassword: "123456"
};
const platform = "android";
const buildConfiguration = "release";
tns.nsCloudBuildService
.validateBuildProperties(platform, buildConfiguration, projectId, androidReleaseConfigurationData)
.then(buildResult => console.log("Data is valid"))
.catch(err => console.error("Data is invalid:", err));
getBuildOutputDirectory
getBuildOutputDirectory
- Returns the path to the directory where the build output may be found.
This method is currently available only for backwards compatibility. The module now implements base module for server operations that exposes same functionality with more generic method:
getServerOperationOutputDirectory
. Detailed description of the parameter can be found here.
Definition:
getBuildOutputDirectory(options: ICloudBuildOutputDirectoryOptions): string;
Detailed description of the parameter can be found here.
Usage:
const tns = require("nativescript");
const cloudBuildOutputDirectory = tns.nsCloudBuildService
.getBuildOutputDirectory({
platform: "ios",
projectDir: "/tmp/myProject"
emulator: false
});
nsCloudCodesignService
The nsCloudCodesignService
allows generation of codesign files (currently only iOS .p12 and .mobileprovision) in the cloud. You can call the following methods:
generateCodesignFiles
generateCodesignFiles
method validates passed arguments and tries to generate codesign files in the cloud. In case of success, the result files (.p12 and/or .mobileprovision) are downloaded. The result contains information about errors, if any, and path to the downloaded codesign files (in S3).
Definition:
generateCodesignFiles(codesignData: ICodesignData, projectDir: string): Promise<ICodesignResultData>;
Detailed description of the parameter can be found here.
Usage:
const tns = require("nativescript");
const codesignResultData = tns.nsCloudBuildService
.generateCodesignFiles({
username:'appleuser@mail.com',
password:'password',
platform: "ios",
clean: true,
attachedDevices: [{
displayName: 'iPhone',
identifier: 'cc3653b16f1beab6cf34a53af84c8a94cb2f0c9f'
}]
}, '/tmp/projects/myproj');
getServerOperationOutputDirectory
getServerOperationOutputDirectory
method returns the path to the directory where the server request output files may be found, if any. In this implementation - the generated codesign files.
Definition:
getServerOperationOutputDirectory(options: ICloudServerOutputDirectoryOptions): string;
Detailed description of the parameter can be found here.
Usage:
const tns = require("nativescript");
const generateCodesignFilesOutputDirectory = tns.nsCloudBuildService
.getServerOperationOutputDirectory({
platform: "ios",
projectDir: "/tmp/myProject"
emulator: false
});
nsCloudPublishService
The nsCloudPublishService
allows publishing build packages to an application store (either GooglePlay or iTunesConnect). You can call the following methods:
publishToItunesConnect
publishToItunesConnect
method -will try to publish the provided package to iTunes Connect.
Definition:
publishToItunesConnect(publishData: IItunesConnectPublishData): Promise<void>;
Detailed description of the parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudPublishService
.publishToItunesConnect({
credentials: {
username: "user",
password: "pass"
},
packagePaths: ["/tmp/myReleaseIpa.ipa"],
projectDir: "/tmp/myProject"
})
.then(() => {
console.log("Publishing succeeded");
})
.catch(err => console.error(err));
publishToGooglePlay
publishToGooglePlay
method will try to publish the provided packages to Google Play.
Definition:
publishToGooglePlay(publishData: IGooglePlayPublishData): Promise<void>;
Detailed description of the parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudPublishService
.publishToGooglePlay({
track: "alpha",
pathToAuthJson: "/tmp/myAuthJson.json",
packagePaths: ["/tmp/myReleaseApk.apk"],
projectDir: "/tmp/myProject"
})
.then(() => {
console.log("Publishing succeeded");
})
.catch(err => console.error(err));
nsCloudApplicationService
The nsCloudApplicationService
allows for application management and gathering more information about the app's current state. You can call the following methods:
shouldBuild
shouldBuild
method will determine whether the current application should be built or not.
Definition:
shouldBuild(config: IApplicationBuildConfig): Promise<boolean>;
Detailed description of the parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudApplicationService
.shouldBuild({
projectDir: "/tmp/myProject",
platform: "android",
outputPath: "/tmp/myProject/.cloud/android"
})
.then((shouldBuild) => {
console.log("Should build? ", shouldBuild);
})
.catch(err => console.error(err));
shouldInstall
shouldInstall
method will determine whether the current application's package should be installed on the given device or not.
Definition:
shouldInstall(config: IApplicationInstallConfig): Promise<boolean>;
Detailed description of the parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudPublishService
.shouldInstall({
projectDir: "/tmp/myProject",
deviceIdentifier: "192.168.56.101:5555",
outputPath: "/tmp/myProject/.cloud/ios"
})
.then((shouldInstall) => {
console.log("Should install?", shouldInstall);
})
.catch(err => console.error(err));
nsCloudEmulatorLauncher
The nsCloudEmulatorLauncher
provides a way for initial interaction with cloud emulators. You can call the following methods:
startEmulator
method - starts an cloud emulator and returns a url where an html page is located, containing an iframe with the actual emulator.
Definition:
interface ICloudEmulatorStartData {
packageFile: string;
platform: string;
model: string;
}
interface ICloudEmulatorLauncher {
startEmulator(data: ICloudEmulatorStartData): Promise<string>;
}
Usage:
const tns = require("nativescript");
tns.nsCloudEmulatorLauncher.startEmulator({
packageFile: "test.apk",
platform: "android",
model: "nexus5"
}).then(address => {
console.log("address is", address);
});
nsCloudAuthenticationService
The nsCloudAuthenticationService
is used for authentication related operations (login, logout etc.). You can call the following methods
login
login
mehod starts localhost server on which the login response will be returned. After that if there is options.openAction
it will be used to open the login url. If this option is not defined the default opener will be used. After successful login returns the user information.
Definition:
login(options?: ILoginOptions): Promise<IUser>;
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudAuthenticationService
.login()
.then(userInfo => console.log(userInfo))
.catch(err => console.error(err));
const tns = require("nativescript");
const childProcess = require("child_process");
const openAction = url => {
const isWin = /^win/.test(process.platform);
const openCommand = isWin ? "start" : "open";
childProcess.execSync(`${openCommand} ${url}`);
};
const loginOptions = { openAction: openAction };
tns.nsCloudAuthenticationService
.login(loginOptions)
.then(userInfo => console.log(userInfo))
.catch(err => console.error(err));
logout
logout
method invalidates the current user authentication data.
Definition:
logout(options?: IOpenActionOptions): void;
Usage:
const tns = require("nativescript");
tns.nsCloudAuthenticationService.logout();
const tns = require("nativescript");
const childProcess = require("child_process");
const openAction = url => {
const isWin = /^win/.test(process.platform);
const openCommand = isWin ? "start" : "open";
childProcess.execSync(`${openCommand} ${url}`);
};
const logoutOptions = { openAction: openAction };
tns.nsCloudAuthenticationService.logout(logoutOptions);
isUserLoggedIn
isUserLoggedIn
method checks if the access token of the current user is valid. If it is - the method will return true. If it isn't - the method will try to issue new access token. If the method can't issue new token it will return false.
Definition:
isUserLoggedIn(): Promise<boolean>;
Usage:
const tns = require("nativescript");
tns.nsCloudAuthenticationService
.isUserLoggedIn()
.then(isLoggedIn => console.log(isLoggedIn))
.catch(err => console.error(err));
refreshCurrentUserToken
refreshCurrentUserToken
method uses the refresh token of the current user to issue new access token.
Definition:
refreshCurrentUserToken(): Promise<void>;
Usage:
const tns = require("nativescript");
tns.nsCloudAuthenticationService.refreshCurrentUserToken()
.then(() => console.log("Success"))
.catch(err => console.error(err));
cancelLogin
cancelLogin
method stops the current login process and rejects the login promise with an error.
Definition:
cancelLogin(): void;
Usage:
const tns = require("nativescript");
tns.nsCloudAuthenticationService
.login()
.then(userInfo => console.log(userInfo))
.catch(err => console.error(err));
tns.nsCloudAuthenticationService.cancelLogin();
Interfaces
interface IUser {
email: string;
firstName: string;
lastName: string;
}
interface IAuthenticationService {
devLogin(username: string, password: string): Promise<IUser>;
login(options?: ILoginOptions): Promise<IUser>;
logout(options?: IOpenActionOptions): void;
refreshCurrentUserToken(): Promise<void>;
getCurrentUserTokenState(): Promise<ITokenState>;
cancelLogin(): void;
}
interface IOpenActionOptions {
openAction?: (url: string) => void;
}
interface ILoginOptions extends IOpenActionOptions {
timeout?: string;
}
interface ITokenState {
isTokenValid: boolean;
expirationTimestamp: number;
}
nsCloudUserService
The nsCloudUserService
is used to get information aboud the current user or modify it. You can call the following methods
hasUser
hasUser
method checks if there is user information.
Definition:
hasUser(): boolean;
Usage:
const tns = require("nativescript");
const hasUser = tns.nsCloudUserService.hasUser();
console.log(hasUser);
getUser
getUser
method returns the current user information.
Definition:
getUser(): IUser;
Usage:
const tns = require("nativescript");
const user = tns.nsCloudUserService.getUser();
console.log(user);
Sample result for user
will be:
{
"email": "some@mail.com",
"firstName": "First",
"lastName": "Last"
}
getUserData
getUserData
method returns the user information and the authentication data for the current user.
Definition:
getUserData(): IUserData;
Usage:
const tns = require("nativescript");
const userData = tns.nsCloudUserService.getUserData();
console.log(userData);
Sample result for userData
will be:
{
"accessToken": "some token",
"refreshToken": "some refresh token",
"userInfo": {
"email": "some@mail.com",
"firstName": "First",
"lastName": "Last"
}
}
setUserData
setUserData
method sets the user information and the authentication data for the current user.
Definition:
setUserData(userData: IUserData): void;
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
const userData = {
accessToken: "some token",
refreshToken: "some refresh token",
userInfo: {
email: "some@mail.bg",
firstName: "First",
lastName: "Last"
}
};
tns.nsCloudUserService.setUserData(userData);
setToken
setToken
method sets only the token of the current user.
Definition:
setToken(token: ITokenData): void;
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
const token = {
accessToken: "some token"
};
tns.nsCloudUserService.setToken(token);
clearUserData
clearUserData
method removes the current user data.
Definition:
clearUserData(): void;
Usage:
const tns = require("nativescript");
tns.nsCloudUserService.clearUserData();
getUserAvatar
getUserAvatar
methods returns the URL where the avatar picture can be downloaded from.
Definition:
getUserAvatar(): Promise<string>;
Usage:
const tns = require("nativescript");
tns.nsCloudUserService.getUserAvatar()
.then(userAvatar => console.log(userAvatar));
Interfaces:
interface IUserService {
hasUser(): boolean;
getUser(): IUser;
getUserData(): IUserData;
setUserData(userData: IUserData): void;
setToken(token: ITokenData): void;
clearUserData(): void;
getUserAvatar(): Promise<string>;
}
nsCloudAccountsService
The nsCloudAccountsService
provides methods for working with accounts. You can call the following methods:
getMyAccounts
getMyAccounts
method returns the accounts which the current user can use. Each user will have personal account and shared accounts. Shared accounts are those accounts in which the user is added as developer.
Definition:
getMyAccounts(): Promise<IAccount[]>
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudAccountsService.getMyAccounts()
.then(accounts => console.log(accounts));
getUsageInfo
getUsageInfo
method returns the usage information for the provided account.
Definition:
getUsageInfo(accountId: string): Promise<IUsageInfo[]>;
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudAccountsService.getUsageInfo("d0ce3ac0-36c2-427f-8d27-955915ffe189")
.then(usageInfo => console.log(usageInfo));
getAccountFeatures
getAccountFeatures
method returns information about all subscription features of the provided account.
Definition:
getAccountFeatures(accountIdOption: string): Promise<IDictionary<IFeatureInfo>>;
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudAccountsService.getAccountFeatures("d0ce3ac0-36c2-427f-8d27-955915ffe189")
.then(featuresInfo => console.log(featuresInfo));
nsCloudEulaService
nsCloudEulaService
allows interaction with EULA - check if current EULA should be accepted, accepting it, etc.
getEulaData
getEulaData
method gives information for the current EULA - url where to find it and if the user should accept it. When this method is called, it will download the latest EULA in case it has not been already downloaded in the current process. EULA must be accepted in the following condition:
- In case it has never been accepted.
- In case it has been accepted before, but current EULA is different, i.e. user had not accepted it before.
In all other cases (current EULA is the same as the one user had accepted before, new EULA cannot be downloaded, but user had accepted EULA in the past), the method will return that EULA should not be accepted.
Definition:
getEulaData(): Promise<IEulaData>;
The returned result is of the following type:
interface IEulaData {
url: string;
shouldAcceptEula: boolean;
}
Usage:
const tns = require("nativescript");
tns.nsCloudEulaService.getEulaData()
.then(eulaData => console.log(`EULA url is: ${eulaData.url}. This EULA should ${eulaData.shouldAcceptEula ? "" : "not" } be accepted.`));
getEulaDataWitCache
getEulaDataWithCache
method gives information for the current EULA - url where to find it and if the user should accept it. When this method is called, it will download the latest EULA ONLY in case it has not been downloaded in the latest 24 hours. That's the main difference between this method and getEulaData
. EULA must be accepted in the following condition:
- In case it has never been accepted.
- In case it has been accepted before, but current EULA is different, i.e. user had not accepted it before.
In all other cases (current EULA is the same as the one user had accepted before, new EULA cannot be downloaded, but user had accepted EULA in the past), the method will return that EULA should not be accepted.
Definition:
getEulaDataWithCache(): Promise<IEulaData>;
The returned result has the same type as the one returned by getEulaData
.
Usage:
const tns = require("nativescript");
tns.nsCloudEulaService.getEulaDataWithCache()
.then(eulaData => console.log(`EULA url is: ${eulaData.url}. This EULA should ${eulaData.shouldAcceptEula ? "" : "not" } be accepted.`));
acceptEula
acceptEula
method downloads the latest EULA (in case it has not been downloaded in the current process), calculates its shasum and saves it in the user setings file. In case any of the operations fails, the acceptEula
Promise will be rejected with the error.
Definition:
acceptEula(): Promise<void>;
Usage:
const tns = require("nativescript");
tns.nsCloudEulaService.acceptEula()
.then(() => console.log(`Successfully accepted EULA.`))
.catch(err => console.error("Unable to accept EULA. Error is: ", err));
nsCloudProjectService
The nsCloudProjectService
allows to manage cloud projects. You can call the following methods:
cleanupProject method
cleanupProject
method cleans all cloud build data which is used for optimizations. The method will clean all AWS CodeCommit and build machine artefacts if they exist.
Definition:
cleanupProject(cleanupProjectData: ICleanupProjectDataBase): Promise<ICleanupProjectResult>;
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudProjectService.cleanupProject({ appIdentifier: "org.nativescript.test", projectName: "test" })
.then((result) => console.log(`Cleanup result: ${result}`))
.catch(err => console.error("Unable to clean cloud project. Error is: ", err));
nsCloudKinveyService
The nsCloudKinveyService
allows working with Kinvey mBaaS. You can call the following methods:
getApps method
getApps
method returns information for all applications of the current user.
Definition:
getApps(): Promise<IKinveyApplication[]>;
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudKinveyService.getApps()
.then(result => console.log(`Apps: ${result}`))
.catch(err => console.error("Unable to get apps. Error is: ", err));
createApp method
createApp
method creates application in the account of the current user.
Definition:
createApp(input: ICreateKinveyAppInput): Promise<IKinveyApplication>;
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
const createAppInput = {
name: "ns-cloud"
};
tns.nsCloudKinveyService.createApp(createAppInput)
.then(result => console.log(`Created app: ${result}`))
.catch(err => console.error("Unable to create app. Error is: ", err));
createAuthService method
createAuthService
method creates identity store. Then it creates authentication service in this identity store. Then it sets the default authentication service in the provided environment. Then it sets the default authentication service in the provided environment to the newly created service. Currently the supported providers are OAuth2, OIDC and SAML-Redirect.
Definition:
createAuthService(input: ICreateKinveyAuthService): Promise<IKinveyAuthService>;
Description of each parameter can be found here.
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
const createOAuth2Options = {
name: "my-oauth2-service",
provider: {
type: "OAuth2",
remoteService: "https://test.com/oauth/token",
options: {
grantEndpoint: "https://test.com/authorize",
clientId: "<cleint-id>",
clientSecret: "<client-secret>",
userIdEndpoint: "https://test.com/userinfo",
scope: "<scope (e.g. openid)>"
}
}
};
const oauth2Input = {
appId: "<app-id>",
environmentId: "<env-id>",
redirectUri: ["https://auth.kinvey.com/oauth2/redirect", "http://example.com"],
authServiceOptions: createOAuth2Options
};
tns.nsCloudKinveyService.createAuthService(oauth2Input)
.then(result => console.log(`Created OAuth2 auth service: ${result}`))
.catch(err => console.error("Unable to create OAuth2 auth service. Error is: ", err));
const createOIDCOptions = {
name: "my-oidc-service",
provider: {
type: "OIDC",
remoteService: "https://test.com/oauth/token",
options: {
grantEndpoint: "https://test.com/authorize",
clientId: "<client-id>",
clientSecret: "<client-secret>",
issuerId: "https://test.com",
scope: "<scope (e.g. profile)>"
}
}
};
const oidcInput = {
appId: "<app-id>",
environmentId: "<env-id>",
redirectUri: ["http://example.com"],
authServiceOptions: createOIDCOptions
};
tns.nsCloudKinveyService.createAuthService(oidcInput)
.then(result => console.log(`Created OIDC auth service: ${result}`))
.catch(err => console.error("Unable to create OIDC auth service. Error is: ", err));
const createSAMLRedirectOptions = {
name: "my-auth-service",
provider: {
type: "SAML-Redirect",
remoteService: "https://test.com/samlp/<some-id>",
options: {
idpCertificate: "<certificate>"
}
}
};
const samlRedirectInput = {
appId: "<app-id>",
environmentId: "<env-id>",
redirectUri: ["http://example.com"],
authServiceOptions: createSAMLRedirectOptions
};
tns.nsCloudKinveyService.createAuthService(samlRedirectInput)
.then(result => console.log(`Created SAML-Redirect auth service: ${result}`))
.catch(err => console.error("Unable to create SAML-Redirect auth service. Error is: ", err));
updateAuthService method
updateAuthService
method updates the provided authentication service.
Definition:
updateAuthService(input: IUpdateKinveyAuthService): Promise<IKinveyAuthService>;
Description of each parameter can be found here.
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudKinveyService.getDefaultAuthService({ environmentId: "<env-id>" })
.then(authService => {
const id = authService.id;
delete authService.id;
authService.name = "new-name";
const updateAuthServiceInput = {
authServiceId: id,
authService
};
return tns.nsCloudKinveyService.updateAuthService(updateAuthServiceInput);
})
.then(result => console.log(`Updated auth service: ${result}`))
.catch(err => console.error("Unable to update auth service. Error is: ", err));
getAuthServices method
getAuthServices
method returns all authentication services which allow access to the provided environment.
Definition:
getAuthServices(input: IGetKinveyAuthServices): Promise<IDictionary<IKinveyAuthService[]>>;
Description of each parameter can be found here.
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudKinveyService.getAuthServices({ environmentId: "<env-id>" })
.then(result => console.log(`Auth services: ${result}`))
.catch(err => console.error("Unable to get auth services. Error is: ", err));
getDefaultAuthService method
getDefaultAuthService
method returns the default authentication service for the provided environment.
Definition:
getDefaultAuthService(input: IGetDefaultKinveyAuthService): Promise<IKinveyAuthService>;
Description of each parameter can be found here.
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudKinveyService.getDefaultAuthService({ environmentId: "<env-id>" })
.then(result => console.log(`Default auth service: ${result}`))
.catch(err => console.error("Unable to get dafault auth service. Error is: ", err));
changeDefaultAuthService method
changeDefaultAuthService
method changes the default authentication service in the provided environment.
Definition:
changeDefaultAuthService(input: IChangeDefaultKinveyAuthService): Promise<IKinveyAuthService>;
Description of each parameter can be found here.
Detailed description of each parameter can be found here.
Usage:
const tns = require("nativescript");
tns.nsCloudKinveyService.getAuthServices({ environmentId: "<env-id>" })
.then(authServices => {
const identityStoreId = Object.keys(authServices)[0];
const authServiceId = authServices[identityStoreId][0].id;
const changeDefaultAuthServiceInput = {
environmentId: "<env-id>",
authServiceId,
identityStoreId
};
return tns.nsCloudKinveyService.changeDefaultAuthService(changeDefaultAuthServiceInput);
})
.then(result => console.log(`New default auth service: ${result}`))
.catch(err => console.error("Unable to change dafault auth service. Error is: ", err));
Development
The project is written in TypeScript. After cloning it, you can set it up by executing the following commands in your terminal:
$ npm i --ignore-scripts
- NOTE: --ignore-scripts
is a must.$ npm i -g grunt-cli
(only in case you do not have it installed globally)$ grunt test
(first execution of this command might take a little bit longer, consecutive calls will work much faster)
After that you can make changes in the code. In order to transpile them, just execute:
You can pack a new version of the library by executing: