wsharba / opendatakit

Automatically exported from code.google.com/p/opendatakit
0 stars 1 forks source link

ODK Collect does not update username field in ProfileManager as the username is changed in the general settings tab. #1037

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Confirmed that the following behavior occurs. This would apply to the username 
and to the e-mail account that are reported by the profile manager. 

---------------
from: Jeffrey Meyers meyers2@pdx.edu

ODK Aggregate v1.4.3 instance running with a PostgreSQL 9.1 database. With ODK 
Collect 1.4.3 (1042) tested on both Android 4.1.2 and 4.4.2.

I an encountering a problem where it seems that if you change the username and 
password in "General Settings" that those changes are not put into effect for 
any subsequently submitted forms until you hard exit from Collect and re-open. 
Here are some steps to follow to replicate my problems.

1) Start by logging in as "User_1" and download a form.

2) Fill out a survey and send finalized form.

3) Go to "General Settings" and change username and password to "User_2"

4) Fill out a survey and send finalized form.

5) Running a query shows both submitted forms are from "User_1"

6) Hard exit out of ODK Collect

7) Re-open ODK Collect fill out form and submit. You are prompted to enter 
username and password, but the username set in Step 3 is already set as 
default. Submitted form is now showing "User_2."

Am I changing users correctly? Is the only way for different users to take 
effect is to hard exit after changing user in "General Settings?" Thanks.

Original issue reported on code.google.com by mitchellsundt@gmail.com on 4 Aug 2014 at 7:53

GoogleCodeExporter commented 9 years ago
Yes, sorry, we discovered and fixed this in our latest SurveyCTO release. I'd 
actually thought it was something we'd broken only in our branch, which is why 
I didn't think that we needed to share the fix. We'll push our proposed fix 
within a week or so (summer vacations permitting).

Original comment by chrislro...@gmail.com on 4 Aug 2014 at 8:28

GoogleCodeExporter commented 9 years ago
That would be wonderful.  Thanks Chris!

Original comment by mitchellsundt@gmail.com on 4 Aug 2014 at 9:13

GoogleCodeExporter commented 9 years ago
I actually am doing this fix myself -- consolidating the JR initialization code 
into one place, since there seems to be some scattered in FormEntryActivity, 
and some in FormLoaderTask.

Original comment by mitchellsundt@gmail.com on 8 Aug 2014 at 12:20

GoogleCodeExporter commented 9 years ago
Thanks, Mitch. Sorry we're slow.

Original comment by chrislro...@gmail.com on 8 Aug 2014 at 12:22

GoogleCodeExporter commented 9 years ago
We took a closer look to this issue's description and it seems that our fix is 
not applicable to this one. We have a fix for a different issue but very very 
very similar to this one. 

If you use some valid user credentials A to download a form, fill up the form, 
then apply some invalid user credentials B and try to upload the form, the form 
will be successfully uploaded by using A not B. The issue is that the cookies 
store is not cleared when the user credentials change.

We will push our fix to that in the "surveycto" branch.

Original comment by mele...@surveycto.com on 18 Aug 2014 at 1:15

GoogleCodeExporter commented 9 years ago
changes are in rev 1044 and higher

Original comment by mitchellsundt@gmail.com on 29 Aug 2014 at 10:44