I had a question about this… I’ve developed an app for a client and am ready to transfer it to their team. It was developed as a free app (because it was only in development and didn’t need any Pro features yet), but the client will be upgrading to a Pro app and will need to collect real email addresses. During development, myself and multiple other users logged in to the app to test it out and, since it was free, the app anonymized the email addresses.
It seems as though (after reading the documentation and the above), that those test users are now stuck with their anonymous emails in the app. It would be great if the Glide Data Editor could take priority here and any changes that are manually made to the User Profiles sheet in the editor are respected going forward — this way, the app developer/administrator could ensure the email addresses are consistent and correct once the app goes Pro.
I think I read another thread where someone got around this by changing the Data Source to a clean version of the same Google Sheets that are used for the app. Before doing that and possibly messing something up, can anyone confirm that this is a process that has been tested and is known to work? I’m thinking that the process could be — transfer the app to client’s team, have client upgrade app to Pro and remove anonymization, make a copy of the underlying sheet, empty the new version of the sheet, change data source in the app. The hope is that new (and previous) users will log in and their real email addresses will be used.
I honestly don’t build a lot of apps for clients, but this seems like something that should work a bit better or be easier to resolve. I don’t think an app should need to start in Pro while it is being developed to mitigate this problem.