I am experiencing an issue with displaying correct user data in a repeating group when using privacy settings which locks data down to the creator.
The privacy condition I am using is when creator(of data) is the current user.
This works fine logging in and out with a user. It displays user data when logged in and hides all data when not logged in.
This will keep on working until you log in as a different user then it won’t display the new users data because it seems the privacy condition is still looking for the first user.
When the page is refreshed it then must recheck the condition server side and starts displaying the new user data.
The problem with this is I am building a native app I don’t want to use the refresh page function.
Does any one know if the server side privacy condition is only run on page load and not when the conditions change.
I see you are having luck with your privacy rules. I have spent days on this one problem and the rest of my app is on hold because of it.
I made a simple example to show you the problem I am having.
Step 3 - User number 1 is logged out and user number 2 is logged in. the page hasn’t been refreshed yet. Note that user number 1 data is being displayed to the wrong user.
This problem happens even when I try to clear the repeating group list and display new list data. The only way I can get this problem to go away is to remove privacy rules and add constraints in the (do a search) feature which makes my data less secure.