Closed dcgs-sbu closed 1 year ago
We have added google identity support now. This is /beta. Please help test.
Thank you. We'll be starting our next Makecode Arcade project in the new year, so I'll do some 'stress testing' then!
On Wed, 28 Sept 2022 at 01:22, Abhijith Chatra @.***> wrote:
We have added google identity support now. This is /beta. Please help test.
— Reply to this email directly, view it on GitHub https://github.com/microsoft/pxt-arcade/issues/4677#issuecomment-1260232308, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTM6B2COASFXJFM3Z5NHQTWAOFUJANCNFSM5PJKFX6Q . You are receiving this because you authored the thread.Message ID: @.***>
Thanks for supporting makecode.
Update: I've now had 180 students sign in to Makecode Arcade using their Google accounts, with no issues that I can discern. It was so much simpler this year, so thank you very much!
Also, I'm really pleased with the changes to the sharing function - updating a static link is great, and the feature to automatically attach projects to Classroom is incredibly helpful! Thank you!
Thanks so much for the feedback.
I am a Computer Science teacher and have recently started using MakeCode Arcade with my students, in place of Scratch. We have run into a couple of issues with the Microsoft account system:
When they were setting up their accounts in the first lesson, they were asked to provide a phone number. We do not allow phones in lessons, so I had to abandon this activity and ask the students to create their accounts at home in time for the next lesson. Having discussed this with you via email, the current theory is that this is a parental permission feature due to the students creating underage accounts - I will test this next week with a small working party of students and update this thread with anything useful we discover.
In subsequent lessons, the sign-in system has proved to be quite trigger-happy in locking accounts. I can't tell if it's lots of students getting their passwords wrong, lots of sign-ins occurring at the same time from the same IP address, or both. However, the main problem is that the process for unlocking an account requires the user to send a message to their phone; so again, when this happens, that student has to abandon signing in for the lesson.
Fortunately, because they can create projects and publish those projects without needing to be signed in, they can 'save' their work by pasting the published link into a document, and then fork that project next time they want to continue with it.
You have said that you are looking at implementing a Google sign-in option - as our school has a Google education account, that would circumvent the entire problem for us, and so would be much appreciated - thank you.