Make manual loading of survey in wrong FLOW app impossible

mtwestra commented 9 years ago

Some mobile users manually transfer a survey from one FLOW instance to a FLOW app from another instance. This can happen when an enumerator collects data using different FLOW instances, and doesn't install the correct FLOW app for a given survey.

Proposed solution: 1) Include the GAE app id in the survey definition XML 2) In the FLOW app, on loading a manually transferred survey, check if the survey XML app id corresponds to the data server as set in the FLOW app. If they don't match, display a toast saying that the survey does not belong to this FLOW instance app.

Corresponding FLOW app issue: https://github.com/akvo/akvo-flow-mobile/issues/242

ichinaski commented 9 years ago

Test plan:

Edit & (re)publish any survey
Ensure the <application> entity contains the property app, which relates to the unique id for the instance.

rumca commented 9 years ago

The above test plan passes as described - survey xml contains the app property. Bootstrap specific behaviour will be tested on flow-mobile issue.

akvo / akvo-flow

Make manual loading of survey in wrong FLOW app impossible #1071