LinkedIn
Twitter
The error message that I'm writing about in this post looks like this:
I ALWAYS get this error when I deploy sample / template apps, even when following the correct procedure I've outlined in my own "tip" on how to publish apps as templates:
It has been my experience that I can ignore this message when I'm sure that I've followed the proper steps. But, I thought I'd write about this to ask why we get errors even when we're not doing anything wrong. Even as an experienced sharer of sample apps, error messages ("Pay up! You can't do this on a free plan!") cause some anxiety. And, of course, I think they cause a lot more anxiety for people who are attempting to publish free samples for the first time. So here's my question: Is there anyone out there who is on a free plan who has been able to publish a template on your portfolio page without having this error message displayed? If so, how?
And here a related question, if I can confirm that this is a problem with the AppSheet platform, not my usage, how do I convey that to AppSheet? Is "Feature Ideas" the proper venue?
Finally, a comment: I'm a big fan of the AppSheet platform, but one pet peeve of mine is that it's rather unfriendly (not intentionally, of course) to user-generated content. For example, user-made templates cannot be searched easily as official AppSheet templates can. In this regard, I'd like AppSheet to be more like YouTube in promoting, recognizing, and valuing user-generated content.
Thanks to both @Joseph_Seddik and @TeeSee1 for your help. I tried it as follows:
Turning off "Require user signin" required me to turn on the two settings you see below.
The sample was fine and I was able to copy it into another account. When copied, the new copied app has the normal "Require user signin?" set to on, which is good. One minor issue I noticed is that I wasn't able to change the name of the app during the copying process:
Note that "Copy app" is greyed out, even after I tried to revert to the original name of the app. This is unacceptable for me.
So, I'm inclined to accept what @Joseph_Seddik pointed out to me as the "solution" because he taught me something I didn't know. But, I don't want the people at AppSheet to think "no problem" because they see a solution. I still think AppSheet needs to fix this. That's the dilemma a feel right now.
