I recently started getting an error saying that I canโt use the =useremail() function without requiring sign in.
The thing is, this was never an issue before.
If the person didnโt sign in, they just didnโt see any of the data.
Now it wants me to sign up for the standard plan, which is ridiculous ($1 per month per user).
Has anyone else dealt with this?
@Alexander_Beard I belive youโre on a free plan. Using the USEREMAIL() function requires the User Authentication set to ON which will require anyone of the per user plan licence
Right.
That function didnโt require user authentication in the past.
Was this an intentional update?
Well I will say that even though I upgraded to the plan the app told me to, our employees still canโt access it.
So, I guess your whole business is just crap now.
@Alexander_Beard I believe you might have a misunderstanding at that point. To read a userโs email address with a USEREMAIL() expression, the user should explicitly log in to your app thru the appโs specified cloud auth provider and therefore to be white-listed on top of that.
No I get it.
However, useremail used to not interfere with the app working at all.
So when a user didnโt log in they didnโt see any user specific data.
When they DID log in, they would then see their personal data.
Now, the app wonโt function unless I REQUIRE sign in.
Iโm getting frustrated because Iโve been using AppSheet since they first began and it was free.
At the time it was cheaper than buying an app already out there.
Even when they started charging me, it was cheaper and I understood.
However, it seems like now they just keep increasing prices on me.
I use this app for tracking staff in a small family business that canโt afford $1 per user per month.
They also donโt offer any customer service unless you pay premium, which is insane since early on I was talking to the founders and developers.
I may just have to close my account on this one.
@Alexander_Beard AppSheet is still offering free usage up-to 10 users per month fora prototype app. But deploying the app and reading the userโs email and slicing the app data as per useremail requires a per-user app plan.
You have a knack for regurgitating the information from the AppSheet website.
Thank you.
@Alexander_Beard Iโm not regurgitating any info. What I have tried to explain is generic for majority of the systems. Thank you.
Easy solution: Remove USERMAIL()
Hello @Alexander_Beard the founders and developers are still around.
Praveenโs post on this available at: plus.google.com - Clarifying user sign-in requirement when using USEREMAIL() As some of you knโฆ
The publisher plans were never intended to support per user or private data.
Those plans were always intended for pure public apps like product catalogs or course schedules.
Clarifying user sign-in requirement when using USEREMAIL() As some of you knโฆ plus.google.com
User | Count |
---|---|
40 | |
34 | |
29 | |
23 | |
17 |