When the user enabled "Auto send" in Form Management settings should schedule submission of the forms currently on the device. Right now forms would not auto submit until another instance was filled out.

Acceptance

• Given I've filled out (and finalized) a form
  And I've still not sent that form to the server
  When I go to Form Management settings (in General settings)
  And I enable

Is your feature request related to a problem? Please describe.

Nope, Just a missing GameMode

I would like to be able to..

I would like to be able to access bentoboxes newest gamemode AOneBlock from the bentobox addon

Please help us help you by filling out the following sections as thoroughly as you can.

Description:
When I start the merge request worker on the gitlab-issues+releases-patch branch, I get one Merge request record partially inserted, these errors:

(augur-gitlab) ➜  gitlab_merge_request_worker git:(gitlab-issues+releases-patch) ✗ cat gitlab_merge_request_worker_51200_collection.e

Replace int mapType

Sentry can use refs to git commits to enhance the error reports we get when something fails. For that to work, Sentry needs to receive some information:

• a list of refs belonging to each release
  or
• the most recent commit of the release
  or
• the most recent commit of the release and the most recent commit of the previous release

[Sentry docs with more info](https://docs.sentry

Context

As part of the research done around user authentication, we also learned about the current concept of public/private status of submissions (akvo/akvo-flow#2559 (comment)).

Currently a survey can be set to public or private. This means that all submissions made to the forms in the survey are shown on Flow's public map (the one showing if you are

Most, if not all, the code has been "ported" from the generated code version from BuilderX.
Check and remove the folder builderX if there's nothing else to use.

Some attributes used by clients result in warnings because Javarosa is not aware of them. #276 removed warnings for some. #283 identifies others that still result in warnings.

All should be passed through except for orx:max-pixel which is still a quite recent addition and can be done right by adding a field.

Software and hardware versions

Android 6.0.1

Problem description

My guess is that this is a regression caused while adding runtime permissions.

Steps to reproduce the problem

Attempt to send a form in Android 6.0

Expected behavior

A prompt should appear to allow the write settings permissions when the below method is attempted to call

Other information

From https://forum.opendatakit.org/t/copy-a-field-into-another/6808/

I wonder if using once() would meet your requirements. The name of this function is not very descriptive as it works like if_empty() and therefore wouldn't override a user-entered value, unless the user-entered value is empty. We should perhaps consider adding an alias for once().