1. What is the problem? Be very detailed.
Collect would update forms/media from Aggregate even if the submissions were made via Google Account to Google Drive. Forms hosted in central are not updating when I switch Server/Account to Google in Collect to submit data to Google Drive..
I have some forms hosted and published in ODK Central as well as few in Google Drive. I use the AppKey to submit data to Central and use my Google account to submit to Google Drive. Forms from both sources show in my Collect App simultaneously as expected and I'm able to submit data as well by switching server in General Settings of ODK Collect.
The problem is that my form data and media does not trigger a form update once I have switched Server to Google Account even through the Central forms still show. Previously with Aggregate the forms/media would still update even when I'd switched to my Google Drive/Account.
I'm happy to provide more information. Perhaps there's something I'm not doing correctly.
When I switch back to my Central in Collect Settings, the updates resume.
I also use some forms in Central that submit data to GoogleDrive as well. The central updates are affected in this case as well.
2. What app or server are you using and on what device and operating system? Include version numbers.
Collect: 1.30.0
Central: 1.1.2 hosted in DigitalOcean
3. What you have you tried to fix the problem?
Tried to change media and version of form hosted in central to see if form update is triggered.
4. What steps can we take to reproduce the problem?
Host an xlsform in Central e.g. formC.xml.
Host an xlsform in Google Drive e.g. formG.xml.
In Collect:
Setup Central Server settings in ODK Collect manually or via QR Code.
Set ODK Collect to automatically update form definitions and frequency of updates to 15 minutes.
Setup Google Drive using on screen options in Server settings by picking one of the Google accounts configured within the android phone.
Switch to Central Server/Account in Collect and download formC.
Switch to Google Server/Account in Collect and download formG.
Update formC hosted in Central and publish it with a new version. Wait for 15-30 minutes to see if the formC version updates in Fill Blank Form in Collect. Form will not update hence reproducing the problem.
If you switch the google account back to Central in Server settings in Collect. Then form update resumes as normally expected.
5. Anything else we should know or have? If you have a test form or screenshots or logs, attach below.
You're doing excellent development in bringing new ODK features to us and enriching roadmap. Thank you. I've also made a feature request to re-instate the expected behaviour in collect/central as food for thought. It's a major hassle/point of confusion for our teams/users.
ODK Collect works in that way that if you switch to google server then automatic updates are stopped.
I can't recall now but maybe in older versions, it didn't wasn't the case and that's why now you are confused.
So it's not your fault and unfortunately, there is nothing you can do to change it.
I am really hoping we can re-enable that as ODK Collect is capable of hosting forms from Central that can submit to Google sheets. It's counter-intuitive to block form update flexibility while submissions are allowed. I am open to suggestions of reasons (other than purely technical) because it's a good part of the product portfolio. It's better let the user pick this as a preference in general settings. Either update based on form source or based on General Settings->Server
Appreciate if this can be shared within your team.
We've also done alot of development that relies on this flexibility. Really hope something can be done about it.
Yeah, this change was made intentionally. Before Collect would continue to run auto update on whatever Open Rosa server had been set up last. It's important to point out that as far as I understand this was never a "feature" of Collect but something that "happened" to work because auto update assumed you were using an Open Rosa server rather than Google Drive.
I think we should close this support thread (@alios82 if you mark this as the answer please) and we discuss this in your feature post.