MobiControl 14.3: No longer able to update Profile packages
- 26 February 2019
- SOTI MobiControl - Android
14 Answers- 3 Upvotes
- 5 Followers
14 Answers
Phew, glad I didnt upgrade yet! I was pretty excited by the number of new features that were a part of this release but I'm not willing to lose that feature in exchange for the new ones!
Yea I waited as well. Normally I wont go up until I see a revision come thru.
I've discovered a workaround to my problem.
I manage my device configurations with separate Profiles: one for settings (WiFi, APN, passwords, etc) and one for Packages. I keep the Profiles separate to keep a "base configuration" across all devices and allow flexibility when it comes to updating packages across several groups.
If a Profile only has Packages listed and nothing else, MobiControl 14.3 fails to save any of my changes. The Profile version does not increase, and a draft is not created either.
As soon as I added a bogus Bookmark configuration and then changed the deployed Package version, my changes were successfully saved. Further changes to the Profile's Packages are saved, as long as a bogus configuration entry is present.
This is definitely a MobiControl bug that seems to have been missed by the developers.
Hello Saro,
Thank you for bringing this to our attention. Have you created a case for this already?
If not please contact us at Support@soti.net so that we can investigate the issue and if necessary put in a request to have it fixed, please.
If possible send me a private message with your case number so that I can follow the case.
Regards,
Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |
Hello Saro,
This was an interesting find.
Luckily, I was able to reproduce this on my local environment and found that the culprit is the Grammarly extension.
As soon as it was deactivated, the profiles dialog began to render the profile configuration form without any issues.
We are working on identifying the conflict between MC and the extension.
Please note that other extensions may cause issues as well.
Wow, nice find! So you're saying that I can install 14.3 now? ;)
Hi, which one of the issues were you able to reproduce? I have mentioned two (2) so far: unable to save Profiles, and incorrectly displayed Package version numbers.
To clarify:
- I am NOT able to save Profiles with only Packages.
- I am able to save Profiles with Packages when a Configuration entry is also present in the Profile.
- The Package version numbers displayed in the new UI are incorrect, no matter if I am able to update/save the Profile or not.
There are no page-modifying extensions present. I have tried the following browsers: Chrome, Edge, and IE 11.
EDIT: I have also tried updating the package directly on the MobiControl server without success. I have even tried different administrative user accounts. Creating a new Profile makes no difference; I just can't save Profiles when only Packages are listed. MobiControl 14.3 wants a Configuration entry present for it to understand that a revision was taken place and save the changes to the database.
Thank you for the clarification. It was definitely a coincidence, which was a result of a misunderstanding.
We should definitely dig deeper into the issue which you are facing in your environment.
Same problem with packages on 14.3. Can support staff please give somes informations about a patch release date ?
Thank for the work around. Just ran into the all package profiles not saving the changes unless I added some other form of policy. Also displaying the wrong version number as well. I hope we get a patch soon.
Looks like this made it into 14.3.1.1189 which was released yesterday:
MCMR-17629 | When a package in a profile was updated with a new version, the package version displayed in the profile does not match the actual version of the package |
Awesome! Might actually give 14.3 a shot now.
great, gonna install that to test server today and see if it works.
Yup, I can confirm the problem was fixed in the recent update.