Why must the Google account be skipped when setting up a device for Skie?

During first setup, Android offers to sign in with a Google account. It is easy to accept, especially on a phone someone has used before. But as soon as an account is on the device, Android treats setup as finished, and the call that sets a device owner fails with an error about existing accounts.

So the rule for an administrator is simple. At the welcome screen choose the language, connect to Wi-Fi if prompted, and when Android asks for a Google sign-in, skip it. If the screen does not show a skip option, check that the device is fully reset and that you are not in the middle of a maker's setup that asks for its own login. Those prompts can usually be skipped too.

If someone did add an account, removing it from Settings is not always enough, because Android remembers that setup has completed. The dependable fix is another factory reset and a clean start. It costs a few minutes and avoids a half-working state.

After Skie is the device owner, accounts are handled by policy. You can lock accounts so none can be added, or allow the accounts your own workflow needs. Students sign in to allowed apps as usual.

Practical tip: write the sequence on a card next to the charging trolley: reset, language, Wi-Fi, skip account, then provision. When a device fails at the first step, an added account is the usual cause. See what to do if another app owns the device.

• Skip the Google account at first setup
• An added account blocks the device owner step
• The fix is a reset, not a workaround
• Accounts can be locked by policy afterwards