I had follow the below instruction from offical wso2 site https://docs.wso2.com/display/EMM220/Data+Containerization+for+Android+Device
But after completed the setup work profile and unstall the agent app from personal profile.
And I have checked my work profile there is no agent app is in accounts page. Please let me know if any solution.
This probably occurs due to an issue in the android agent. To fix it, you can edit the following line and set the android:exported to true.
https://github.com/wso2/product-emm/blob/master/modules/mobile-agents/android/client/client/src/main/AndroidManifest.xml#L99
<receiver
android:name=".services.AgentDeviceAdminReceiver"
android:permission="android.permission.BIND_DEVICE_ADMIN"
android:exported="true">
Once you have done this, you can re-build the agent application and then you will be able to generate the work profile successfully. Fix for this issue should be available with the next release.
Related
I just upgraded to Xcode 8.
Started getting this error when i try to run my app on my iphone:
Things i have verified
My iphone is listed in the dev portal with the correct UDID
I have removed and re-added the provisioning profiles many times in xcode
Any ideas guys?
Do you have automatic code signing activated? What's the log output of the Sign step (see Report Navigator for a specific build)? Does the Sign step use your correct Signing Identity and Provisioning Profile? If not, you need to open the project's General Tab and either
activate Automatic Code Signing
(Check "Automatically Manage Signing")
or configure the Development Team and Provisioning Profile yourself
Created MFP CF app in Bluemix. Push notification was also working fine with GCM. Today saw a messages that there is an update for MFP in the Bluemix dashboard and clicked "Recreate" button. Server was recreated and all my apps and adapters were gone. Then from my development environment pushed the app and adapters and went to console to configure push notification and add the GCM details. Found an error at the top and now I don't see the text box to add the "Server API Key" and "Sender ID"
Looks like the new update got this issue. Is there a way to fix it or backout and go to the previous version?
Any help would be appreciated.
There is work to assure that such events will not happen, however please note this very important notice about the Mobile Foundation Bluemix service, with the Developer plan:
https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/bluemix/using-mobile-foundation/
Note: the Developer plan does not offer a persistent database, as such be sure to backup your configuration as explained in the Troubleshooting section.
Such data loss may occur.
For now you will need to reconfigure your GCM credentials in the console.
I am trying to deploy a node app on heroku via the web GUI for dropbox, and I get the error:
Item could not be modified:
"Content-Type" request header must be set to "application/json".
Any clues as to what that might mean?
Disclaimer: I was not the one who wrote the app, just made two mods for heroku.
In case you haven't found an answer... I have the same problem.
You probably need to update your runtime stack.
Here's Heroku's message on their website:
"The legacy Cedar-10 stack has been deprecated and reached its end-of-life on November 4, 2015. Applications may continue running, however you will not be able to push to your application without upgrading to Cedar-14 first."
How to update informations are available here:
https://devcenter.heroku.com/articles/cedar-14-migration#upgrading-the-production-app-to-cedar-14
I have the same problem. I raised a ticket at Heroku. They replied,
"Are you using Firefox? We seen this recently with Firefox and we are currently working on a fix. In the meantime, you can use another browser like Google Chrome for deploying your app."
And using Google Chrome fixes the problem.
I am testing WSO2-Emm system for managing our android mobile app. We have an app for taxi drivers. We deploy it using our tablets and a single gmail account. Our problem is that google allows up to 10 signed in devices for a single google account.
I have tried to load the apk to the WSO2 store. The problem is that when I want to upload a new version of the same app I get a warning message saying that this APK already exists in the store. When I try to rename it and add it as a new apk it works. The problem is that when I go to App-Management, the application appears under 'installed'. The Emm system doesn't detect there is a new version.
To be more specific, my question is is there a way to manage mobile application versions using the WSO2 store and not the google play store.
If there is a way we can go on with this system. If not, we will stop testing it.
The only way I've figured out how update an already installed app is by going to the App Management tab, selecting your latest version of the app in question, and hitting the install button under the Roles tab (NOT the Users tab). It will send the install command to any devices listed under roles you have checked, even if they already have the app installed. Keep in mind this will install the app on all the devices, even devices that already have the version you're trying to put out.
It looks like you already know about the patch on EMM-686 that must be implemented in order to upload multiple versions of the same app to the Publisher. Just in case you want to confirm it's implemented correctly, see my answer here for instructions on how to implement it.
I'm testing the implementation of the emm, and as i understood in the documentation i can
Automatically install applications WITHOUT end user intervention
Block any application to prevent its installation
Automatically UNINSTALL any app without end user intervention
I tried to perform this tasks using Policies but it didn't seem to work.
I'll appreciate your help.
Thanks.
Gabriel.
You need to configure WSO2 EMM in order to get it working. However for Android devices silent installation and uninstallation does not work until you install the Android Agent app as a system app in your devices. So it will prompt a message to user when EMM server perform an installation or uninstallation operation on the device. But for iOS it happens without use intervention.
if you blocking an app, EMM 1.0.0 shows an warning message to the android users to remove it. and for iOS it actually block the app.
You can use policies to block apps and install apps to the devices.
For iOS you need to configure it according to the documentation in order to get it working. For Android it works without any configurations, but if you are going for production you need to configure it.
I got around this issue by rooting the Android devices we're using and installing the Xposed Framework, along with the XInstaller module for it. There are several options for installation/uninstallation that can be used to create an installation/uninstallation experience free from the need for user intervention.
This was pretty easy for me to do, as we're only using corporate-owned devices that don't even leave the facility. Your mileage may vary.