on 11-23-2012 8:26 AM
Dear Forum Members,
An Android application is compiled with Afaria client libraries, After successful compilation, the application is installed to the device via "Enterprise Android" application policy.
In the policy, the 'apk' file is uploaded and also attached the "application configuration" details to the policy. The user installs the application from the Afaria client, but the configuration details are not reflected.
Please look at the snapshot of the 'configuration' file that was uploaded to the Afaria Server.
{
"autoReleasePeriod":60,
"availableColor":"132E71",
"backgroundColor":"222222",
"darkColor":"132E71",
"deviceAccountId":"",
"devicePassword":"",
"gracePeriod":20,
"lightColor":"F25B0A",
"WebPortalUrl":"",
"refreshTime":2,
"reservedColor":"F25B0A",
"secureDeployment":false,
"textColor":"FFFFFF",
"titleColor":"FFFFFF",
"unavailableColor":"919191"
}
Can anyone please help with right procedure for app onboarding ?
Did you use getSettingsFromAfariaForUrl. This is what we use in iOS. Do you have something similar in Android??
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vijayendra,
In Android also you do have get settings and get certificate as well.
So, you can maintain your server settings (back-end/server where your application should connect) in configuration settings and get them from your application through afariaSLL library.
Make sure, you install application (.apk) from afaria client and then launch it. Then you will be able to fetch configurations settings.
You can also, get certificate from afaria server for your user to onboard to your backend.
Regards,
Abhishek Joshi
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.