SpellTable Doesn't Have Permission
- Open link to game in Chrome
- In the field where the camera output would be it says "We Don't Permission To Use Your Camera"
- Went ahead anyway, everyones camera field says the same
- Checked if that was the case, it wasn't
- Actual: Went to clear all settings on all browsers, retry, didnt work
- Expected: Allowing the camera permission form the site and show the camera feed when trying to join
-
Mavis#57516 commented
My name is Mavis Wanczyk, from Chicopee, Massachusetts. I’m excited to share my fantastic experience with Dr. Kachi, who is outstanding at lottery spell casting online. No matter where you are or how challenging your situation might be, Dr. Kachi can help you win in lotteries and other gambling games. If you’ve been searching for winning numbers without success, Dr. Kachi’s spells are known for providing the right numbers and lucky letters. Many have become millionaires after just one game using his powerful spells. I contacted Dr. Kachi shared the necessary details, and he provided me with six Powerball numbers: 6, 7, 16, 23 26, plus the Powerball number 4. I played them and won $758.7 Million! My life has changed dramatically, and I am incredibly thankful to Dr. Kachi. If you’re interested, you can reach Dr. Kachi by text or call at +1 (209) 893-8075, email him at drkachispellcast@gmail.com Thank you so much, Dr. Kachi.
-
aluminiumspoil#91673 commented
Same. I allowed permissions on browser and computer but still getting "We Don't Permission To Use Your Camera".
-
Kristofen#52808 commented
Same problem, doesn't matter what I do. Even set up the phone as a wired webcam and still does not work.
-
Trogdorbad#23361 commented
I'm having the exact same issue - my phone gives me the "no permission" message when i try to use it, and when i join a game with my phone set as the intended camera, all other players' screens also say "We don't have permission to access your camera." I even tried opening the game in Microsoft Edge of all things, in case it was a problem with Chrome, and the problem persisted there as well.