Incidentally, the Monitor for the app that has been requested for deployment contains the email addresses of specific users who appear to have accessed this sample app.
(It may simply be that I hadn’t noticed this before, but)
This is the first time I’ve realised that the email addresses of users who access the sample app are recorded in the app developer’s app in this way.
I feel this poses a significant security risk…
Has this always been the case?
Furthermore, I have never made this app publicly available.
Thanks for referring to my post. Even though I wrote the instructions and I think they are probably OK, I have made mistakes and gotten similar notifications after publishing my own apps as samples. There may be a new issue that I am unaware of but I can say that in my own case, carefully checking my settings against the recommendations in the “tip” post has helped me in the past. The other thing I can say is that the “deploy!” notification may not disappear right away. After the settings have been corrected, it seems to take the platform some time to recognize it.
Apologies in advance if my comments are not relevant to your situation. I hope support responds quickly and is able to locate the problems.
If something should be corrected in my post (or if there’s a new issue that makes sharing like this difficult) please post an update to let me know.
I would expect anything accessible through your portfolio page would not count against your monthly use limit. The concerns come, I’d think, if the user accesses your app (not a copy they made) directly, outside the portfolio page.
Thank you for your kind words. I hope you get a good resolution soon. Actually, if you don’t, that would be a problem for me too, I think, because publishing new versions of my app as templates / samples is important to me. I’ll continue to follow this thread.
Thank you very much for taking the time to reply despite your busy schedule!
Incidentally, rather than including the sample app in my portfolio, I published it by creating a separate URL for the app, as shown in the diagram below.
I’d like to check with you again: is my understanding correct?
・Copy and Customise… not counted
・Look under the hood… not counted
・Preview operations on a smartphone screen… counted
I had simply published this app as a ‘sample app’ and had never registered any other users via the ‘Share’ button.
Furthermore, I had never made it a publicly available app accessible to all users.
If I assume that this issue occurred because the user was counted as a result of an action taken via the smartphone preview screen of the sample app’s public URL, everything makes sense. I therefore believe the cause was likely an action taken via the smartphone preview screen of the published sample app’s URL.