Issue: Entering the a phone number into the sms verify page results in only a spinning loading icon and no message sent.
Workaround: After checking the browser console for the following error below, you can edit the url parameters to remove the platform parameter and it *may* now work.
[quote] 72.cf1f22b9.chunk.js?daf84f4bf17a435bfa76:2 Uncaught TypeError: Cannot read properties of undefined (reading 'push')
at _ (14.90ac5361.chunk.js:2:73187)
at onSubmit (14.90ac5361.chunk.js:2:73719)
at Object.Pe (72.cf1f22b9.chunk.js?daf84f4bf17a435bfa76:2:1398346)
at Be (72.cf1f22b9.chunk.js?daf84f4bf17a435bfa76:2:1398500)
at 72.cf1f22b9.chunk.js?daf84f4bf17a435bfa76:2:1418512
at zr (72.cf1f22b9.chunk.js?daf84f4bf17a435bfa76:2:1418606)
at Lr (72.cf1f22b9.chunk.js?daf84f4bf17a435bfa76:2:1419021)
at 72.cf1f22b9.chunk.js?daf84f4bf17a435bfa76:2:1424474
at Xu (72.cf1f22b9.chunk.js?daf84f4bf17a435bfa76:2:1488310)
at Ae (72.cf1f22b9.chunk.js?daf84f4bf17a435bfa76:2:1397478).[/quote]
Theory: With the site's JS throwing a TypeError my guess is that the SMS Validation app is designed to accept a Hashmap of like {'phonenumber':'1555555555'} with the included url parameter it is getting an array of hashmaps like [{'phonenumber':'1555555555'},{'platform':'steam'}] and throwing the error and failing *secure* on not handling the unexpected array.
Your role as a moderator enables you immediately ban this user from messaging (bypassing the report queue) if you select a punishment.
7 Day Ban
7 Day Ban
30 Day Ban
Permanent Ban
This site uses cookies to provide you with the best possible user experience. By clicking 'Accept', you agree to the policies documented at Cookie Policy and Privacy Policy.
Accept
This site uses cookies to provide you with the best possible user experience. By continuing to use this site, you agree to the policies documented at Cookie Policy and Privacy Policy.
close
Our policies have recently changed. By clicking 'Accept', you agree to the updated policies documented at Cookie Policy and Privacy Policy.
Accept
Our policies have recently changed. By continuing to use this site, you agree to the updated policies documented at Cookie Policy and Privacy Policy.