I'm trying to turn on Kiosk mode for an non-managed chrome box following the official instructions but when I'm on the chrome://extensions page in developer mode there is no Add kiosk application option.
Did this get removed at some point leaving kiosk mode only available to managed devices?
Edit
The kiosk mode app I was using was a simple one that I wrote and had loaded via the "unpacked extension" box on the extensions page.
Then I published it restricted to test accounts and included the account on the chromebox as a tester and loaded it from the chrome web store that way. The effect is the same and I still don't see the kiosk application options.
Double Edit
I published it unlisted and installed it. The app installs and works. I have "kiosk_enabled" : true in my manifest and I still don't see any kiosk mode option.
Got the manage kiosk button to show up by:
Removing other users. The first user on the machine is designated the owner. I was trying for kiosk mode from the second user.
Restarting the device
After the reboot the Manage Kiosk Applications button was enabled. The solution is hinted at in this bug from 2014: https://code.google.com/p/chromium/issues/detail?id=385943
Related
I followed all recommended steps for setting up a PWA which can be installed on the user device, following the guideline here: Installable PWAs (MDN):
To make the website installable, it needs the following things in place:
- A web manifest, with the correct fields filled in
- The web site to be served from a secure (HTTPS) domain
- An icon to represent the app on the device
- A service worker registered, to allow the app to work offline (this is required only by Chrome for Android currently)
Still, I don't see the browser-default installation prompt.
How do I find out, why my PWA cannot be installed?
I recommend using Lighthouse, which is an excellent tool for auditing your web app with respect to different categories, including PWA properties. It is also available in Google Chrome in the developer tools (Ctrl-Shift-I / Cmd-Opt-I and select tab Lighthouse).
How do I trigger a PWA audit in Lighthouse (in Google Chrome)?
Choose the category Progressive Web App and then click on Generate report.
Example report
In the example below, you can see that there are some issues present. But the reason, why you don't see the installation prompt is the service worker. Apparently, it isn't registered as expected.
Web app manifest or service worker do not meet the installability requirements
I have 5000 devices enrolled with EMM using android management API and recently I am getting issues with multiple devices out of nowhere and getting and error prompt after scanning the QR code on re-enrollment. All of my enrolled devices are Samsung Tab with the older version of android(7-9) and the issue doesn't seem to be related to the android version. Also, The issue has been experienced for the device which was earlier enrolled and was working fine but recently has this issue, we tried re-enrolling it but it gives us the same following error prompt after QR scan.
Cannot create a work profile - The security policy prevents the
creation of a managed device because a custom os is or has been
installed on this device
For your kind information, there is no custom os installed on the device and the device is not rooted or bootloader is not unlocked. I have researched a lot over the internet but cannot find a solution to the problem I have tried following approaches but it doesn't seem to work in my case
To fix this, you will need to update the time on the device by either connecting to wifi or cellular data (insert SIM-card), or by manually changing it in the set-up screen. After this is done you will be able to provision the device.
Tried DPC Identifier method for enrollment, When prompted to sign in on fresh factory reset device, enter afw#setup, which downloads Android Device Policy. Scan a QR code or manually enter an enrollment token to provision the device.
None of the above seems to work for me, I have also seen that its an issue related to Samsung Knox version, so can anyone from Samsung or google help me debugging and solving this issue, will removing the Knox app from the device work in my case.
Eagerly awaiting for the response as most of my device has started getting affected with this issue, please let me know your thoughts and resolution on this.
Not sure if that's an option for you as you have multiple devices, but on my single device, manually downloading and installing "google apps device policy" resolved the issue.
Been a lurker for a while and posting for the first time
Work as IT helpdesk and found a fix for us (context below)
We use Azure, InTune and Samsung Knox
Needing to assign a Knox profile so an application installs and runs
How we fixed this
Unassigned Knox profile
Ran tablet normally, skipping setup of Google, Samsung account and security
Running Samsung updates until current (24th Feb 2021)
Reassign the Knox profile
Factory resetting through settings
run through the setup process
Error has stopped at this point
You can either use Wi-Fi or SIM Card Data for OS updates through Knox
I had the same problems and this is how i fixed it. I have Samsung Tablet Android 10 and need to set it up under Enterprise.
Straight out of the box, you expand the OS, set up Network connection and than type in the google gmail space: afw#mobicontrol. This Does Not install the custom OS. Once expanded the OS has all the bloated software in tact plus the Mobicontrol app. I kept getting an error 'Can't Create Work Profile because Custom OS is installed on this device'. I did a factory reset but did so by powering it off than using the Power Button and Up Arrow to force it to the Android Recovery Screen. There is a factory reset option to choose from. "This Does Not Work". It still keeps the bloated software in tact.
You need to expand the Android OS first than do a reset. Go to SETTINGS. than ABOUT. at bottom is a RESET option. Choose that. Choose Factory Reset. This will delete all those apps. It reboots. Now you can enter afw#mobicontrol at the google email screen and it will install the custom OS and works under Soti.
Reset From the SETTINGS and do a Factory Reset. Than type in AFW#MOBICONTOL and the custom OS will work.
I built an action and it works well through the Home Simulator but I am not ready to make it available publicly yet. Is it possible for me to put it on my Google Home device and also share it with a few coworkers? If so, how? Thanks in advance!
If you are developing your agent in api.ai you can go to the "Interactions" section and enable "Google Home". There you enable Google home and go to the settings. There you can authorize api.ai and enable the preview. Now you should be able to start your agent by saying "start <your agent name from the dialog before>". However this is restricted to your own Google Account you cannot share that in other ways yet.
Check my screenshot I called my project "Playground" after clicking on "Preview" I was able to start my agent in the web simulator by writing "start playground".
I'm developing a LOB (Line-of-Business) UWP project, we're hoping to distribute the app as a .appxbundle file, alongside a .cer and a Powershell script. This is what is generated in the package for you when you generate a bundle from Visual Studio by selecting Project->Store->Create App Packages...
The problem I have is that the Powershell script, Add-DevAppPackage.ps1, has a check for a developer licence in it. Specifically it calls the powershell cmdlet Get-WindowsDeveloperLicense. If this doesn't return anything it sets a variable which eventually calls Show-WindowsDeveloperLicenseRegistration which shows a popup forcing the user to put their Windows 10 device into 'Developer Mode'. If the user doesn't do this, then the Script fails and the user can't install the app.
If we remove this check for a Developer Licence, the script acts as I'd expect and Installs the App, alongside the certificate, with no issues when the Windows 10 machine is either set to 'Sideload Apps' or 'Developer Mode'. The problem now arises when the users device is in the mode of 'Don't use developer features'. The script crashes.
Is there a way of finding out if the current device is in 'At Least' Sideload apps mode, and if it isn't, show a dialog to prompt the user to enable it?
Currently users have to enable Developer Mode to be able to sideload an app, which I'd prefer they didn't have to do. I'd fully expect users to only have to enable 'Sideload apps'
Is there a way of finding out if the current device is in 'At Least' Sideload apps mode, and if it isn't, show a dialog to prompt the user to enable it?
AFAIK, there is no way to detect whether the Sideload apps mode is enabled for now. And we have no access to show a dialog to prompt the user to enable the sideload apps.
The problem now arises when the users device is in the mode of 'Don't use developer features'. The script crashes.
This is because when install apps in Sideload apps mode, you need to install the app with its trusted certificate. All UWP apps must be signed with a certificate.
Currently users have to enable Developer Mode to be able to sideload an app, which I'd prefer they didn't have to do. I'd fully expect users to only have to enable 'Sideload apps'.
Before create the package of your project, you can open the manifest file and in the Packaging lable:
Here you can choose which certificate to use to sign your app. If you don't want to modify this, it's OK, cause when you packaging your app, a certificate file will automatically generated, and you said you are hoping to distribute the app as a .appxbundle file, alongside a .cer and a Powershell script. In Sideload apps mode, the Powershell script file is not needed. You can just copy the .appxbundle file and a .cer file, and
Enable the Sideload apps mode.
Click the .cer file to trust this certification.
Click the .appxbundle file to install your app.
When the Sideload apps mode is enabled, please don't use .ps1 file to install the app.
I am testing my Windows 8 app by logging in as the guest account. I want to see how it works installing with limited permissions.
It seems I cannot debug any apps. Here are the steps:
Login as the Windows 8 Guest Account
Open Visual Studio.
Create a new Windows Store app, using the grid template
Click the play button to deploy to the simulator or the local machine.
Upon deployment, I receive this error:
Unable to debug Windows Store app App1/App1/bin/Debug/App1.exe
The debugger was unable to find the registration for the target application. If the problem persists, try uninstalling and then reinstalling the application.
Am I unable to deploy apps without being an administrator? If not, is there a way around this problem?
It doesn't make sense to try to debug installing an app as a guest. Guest accounts are not allowed to install apps. There is a short forum post regarding accounts here.
If you are wanting to see how the app performs for a guest after it has already been installed, you can run the app from the desktop tile, but I don't know how to run the debugger on it, or even if you can.