Continuing the discussion from eGate-Android MDM-version 1.20-1.25:
Moving to a new topic, because the last one was too long.
Continuing the discussion from eGate-Android MDM-version 1.20-1.25:
Moving to a new topic, because the last one was too long.
Can I install an update to eGate when the option to block app installations is enabled?
No, that option has to be disabled.
Maybe if @FlipAdmin agrees to add OTA updates, that can be bypassed though…
If apk install is blocked can i still update an app on the play store?
No
That would be an amazing update - OTA updates
Shouldnt even be so hard - use REST API endpoints for releases - GitHub Docs
Hi I saw in the last thread some1 else had this problem but they didn’t tell how to fix, I logged into e-gate (ver. 1.22) but exited be4 setting a password and now I’m stuck, anyway to fix?
Use version 1.25. If eGate has an empty password, it will automatically bring up a password reset window.
Got it tysm
I’m setting up eGate on a Qin, have both the regular egate APK and external accessibility APK installed, the ‘enable accessibility filter’ and ‘use external accessibility service’ switches are enabled, but accessibility based features like ‘block webview controls in all apps’, and ‘disable app view in settings’ don’t work.
When I toggle the ‘use external accessibility service’ switch off, those functions start working, but it sounds like from what I’ve read here that I’m going to run into problems if I leave that switch off.
@FlipAdmin Maybe his ROM doesn’t need the external accessibility service?
What problems does it have on the Qin when not using the external accessibility service?
How do I know if I need it or not?
That ROM should need it. I guess debug with @FlipAdmin
But I’m not running into any problems.
Anyone?
I have a customer waiting for his phone back…
Anyone?
Does the accessibility stop working if you exit eGate?
No.
Then you are fine.