e-mission / cordova-connection-settings Goto Github PK

Few more cleanup issues for #9

• move the "set settings" code to a separate module
• set a client field in the profile when the user switches to a different client (at least by URL)
• reflect the results of the user prompt back to the diary (will be tracked in a different bug)

Now that the connection settings can be saved through JSON, we want them to be included as part of the UI channels so that we can have different projects use different hosts even if they only choose to use custom channels on the same native app. We can do this by including custom JSON files into the deployed channel.

Now that we can connect successfully to localhost, we can see whether this really works.

Almost every project so far has wanted to run its own server: the cci-berkeley project, the open sidewalks project and potentially the Brazil class server project. The only project that wants to reuse our server is the Santa Rosa commute survey project.

And several of these want to use ionic deploy to switch instead of deploying their own apps. So we need to make the connection settings configurable at runtime, instead of having them hardcoded in the native code.

I ran into this issue while testing #9.
Both android4 and iphone4 eventually went to continuous (non-duty cycled) data collection with no further user interaction.

Note from #9 (comment)
that the other settings are put into the database on plugin initialize.

The problem is that when we switch to a different channel while clearing out the usercache, the other settings are cleared too. So if we don't force-kill the app, which we typically don't, there is no entry in the database. And then when we sync, if there is an overridden entry on the server, then we end up with an overridden entry on the phone.