Phones and sign-in · Joripo documentation

Joripo Collect says "Waiting for approval"

The phone is new for that person and the organisation's rule holds new phones, or the person is an owner or manager, whose new phones always wait. An owner or manager approves it on Collect, under Joripo Collect devices; the phone asks again by itself every few seconds. See Signing in on Joripo Collect.

The person's password was set by an owner or by the server's maintainer and is temporary. Neither Joripo Collect nor ODK Collect can change a password: the person signs in once on the web, at the address the message names, chooses their own, and then signs in on the phone.

The phone signs in but lists no form

The person may not collect in the workspace that holds the form: an owner checks People › Edit › Workspaces. A reviewer does not collect at all.
A device key can be limited to some of the workspace's forms (Forms on the key).
The workspace may be archived or deleted, or the organisation suspended. Nothing is offered or accepted then.

The phone scans the code, then reaches nothing

The code carries the server's public address. A server set up with a placeholder or a local address such as localhost hands out codes with which the phone tries to reach itself. Joripo checks that an address answers as this server before it puts it in codes and links, and otherwise tells the maintainer under Server administration › Device address. See Reaching the server from the field.

A phone that worked is now refused

It has not checked in for 30 days. A phone's keys stay valid for 30 days after it last reached the server. It recovers by itself the next time it is opened online, and nothing on it is lost.
It was revoked, or its person was deactivated, or given a new password together with signing out of every phone. It signs in again and is approved like a new phone.
The workspace was taken away from the person. Giving it back makes the same key work again.

Forms stay under "Not sent"

A form leaves the phone only when the server answers that it was stored. Until then the phone keeps it and tries again with increasing waits, and Not sent shows each form's reason, using the server's own message when it refused. Common reasons are no connection, a revoked or expired key, an archived workspace, a suspended organisation, or the server in maintenance mode. Fix the cause and press Send; nothing needs to be filled in again.

A phone out of coverage for weeks can export its forms to a file, which a manager imports on the console; see Filling, saving and sending.

The server's address changed

A server run from a laptop through a quick tunnel gets a new address at every start.

Joripo Collect: Settings › Server address, then type the new address or scan the code on its /app page. The app checks that it is the same server before it moves its keys there.
ODK Collect: make a new device key and scan it; the old key's code names the old address.

If Joripo Collect says the new address is a different server, the server's identity changed with its secret key, and the phones must sign in again there.

Too many wrong passwords

Eight wrong passwords for one account, or thirty from one network address, within 15 minutes, block further tries for a while, on the web and on the phones alike. Wait, then try again with the right password. An owner can set a new password, and the server's maintainer can lift a lockout from Server administration.

ODK Collect refuses the email and password

ODK Collect's password sign-in works only when an owner has turned it on, only over https, and only for owners, managers and data collectors. Over plain http the password would cross the network in the clear, so it is refused. Use a device key instead. See Using ODK Collect.

Signed out in the middle of work

A sign-in ends after two hours without use, and seven days after it began however busy you are. In the form editor, the tester and a web form, Joripo asks you to sign in again in a new tab, and Try again sends your work when you come back. See Accounts and signing in.