I recenty made a website using aframe and glitch , when the website is on glitch everything works fine , but once I uploaded into my host everytime appears a pop up asking for device sensors permision
"access this site over HTTPS to enter VR mode and grant access to the device sensors."
Do you know how can I stop this pop up to appear ?
Thanks
You could also deactivate the device orientation permission modal by deactivating it with the following configuration:
<a-scene device-orientation-permission-ui="enabled: false"></a-scene>
Read more about it in the docs:
https://aframe.io/docs/1.1.0/components/device-orientation-permission-ui.html
Keep in mind, that you need aframe version 1.0.0 or newer.
Serve your site over HTTPS. DeviceMotion and WebXR APIs are not available over HTTP
Put this in your CSS:
.a-modal {
display: none!important;
}
Related
I have installed Google Tag Manager on my sites but since the new version of Google Tag Manager, I cannot use the preview option. Each time I click on it, I see my website page opening but get then the following error: "Tag Assistant could not connect to a tag on..A timeout occurred while attempting to connect."
How can I resolve this issue?
Thanks
Best
I noticed that I had my ad blocker on. When I turned it off, it worked.
I had the same problem. On this new version, before use the preview mode, you need to submit at least an empty container, then perform your preview mode like always.
I had the same problem. Opening GTM in incognito and then running the preview mode fixed it for me. I'm guessing its one of my extensions.
Facing ERR_CERT_COMMON_NAME_INVALID, while loading css and js files in chrome browser.
While loading login.aspx page related css and js files are loading in IE and Mozilla where as in chrome its not loading. We have deployed the existing application in new server, same application is working on different server. Is there any configuration to be modified in IIS? I have verified both the environment which looks identical, any specific related configuration is helpful. please find the screen shot below
Screen shot
ERR_CERT_COMMON_NAME_INVALID is a very popular SSL error during loading the website. In most cases, the issue is due to certificate misconfiguration on a server. However, it may appear due to antivirus and firewall or aother third-party extensions. so you can try the following methods to solve the problem.
Check date and time are proper
Your Chrome browser will show ERR_CERT_COMMON_NAME_INVALID error in case the date and time are wrong on your computer or mobile device. Please recheck and adjust it on your via PC settings.
Check browser extensions
In some cases, the problematic browser extension could be a reason for the error. First of all, try to open the website in Incognito window and if that solves the issue then no need to check extensions. Otherwise, follow the next steps:
1.Click the "three dots" button on the top right corner of your browser window
2.Select More tools and Extensions
3.Turn off extensions one by one to find culprit extension and delete it to fix the browser error.
Check Installed SSL certificate
In Chrome, you have to click to the "Not Secure" button located on the left side of the address bar, and then click to "Certificate". There you will see the details of SSL certificate using the field "issued to".
Clear the SSL cache
The browser's SSL cache can be an issue. You have to try clearing the cache to resolve the error. click "Three dots" button on the top right side of the browser, find the "Settings". There you will find "Advanced settings" at the bottom of a page. Now find "Open Proxy Settings" and there you will see the "Content" tab with "Clear SSL state"
I have an Angular application with CSS in it.I have recently changed the CSS and deployed it on server but it is not getting reflected in the client machines.
I have done the following things:
Clear cache and did a hard refresh (Ctrl+f5).
Changed the version number of the CSS file and redeployed it.
Opened developer tools and disabled Cache and reloaded.
Pressed F12, go to source and checked the CSS file if new changes are getting loaded. New changes are there.
When I opened the web application in a new machine, the new changes are getting reflected.
When can be the possible reason for CSS not getting reflected even after checking all the above. Is there anything which I'm missing?
is it a PWA (progressive web app)... ? in which case the data is served by service worker and not freshly fetched.
Go to
Chrome developer tools (press F12)...
Click on Application tab on
the left navigation, click on "Service workers" and 'unregister"
service workers...
going on the next option in the left navigation, click on "Clear storage"...
click on the "Clear site data" button on the right zone restart Chrome and check with Ctrl+shift+R
if you're using a CDN, you may have to purge the cache for this particular CSS file from there as well.
Make hard refresh (Ctrl+Shift+R)
or go to view page source and the open css file from it and make it refresh and then again make hard refresh...Your problem will be solved
Please clear the browser history of the application complete from begin and perform hard refresh and then try to login to your application
You can disable cache in development tool in chrome.
Go to Developer tool in Chrome by pressing F12, Network-> click on Disable Cache
I faced similar issue. This helped me. Hope it might help some one
I'm trying to download google-services.json from firebase console. The error is There was an error. The config file cannot be downloaded at this time. as it can be seen in the below screenshot.
There are answers on Stackoverflow which didn't work for me (one and two). Specifically, clearing cache and history, using a newly installed chrome, trying with firefox and edge, using incognito tabs, didn't work.
What else can be done to get rid of this annoying error?
For me also I had this issue. Before trying anything, I refreshed/reloaded my page, and it works. After refreshing my page, I was able to download google-services.json file.
I had the same problem for a while with firebase google
what I did was to open the Developer Options for the web and looked at the request response from google
and I found out that the network response is very clear:
"The Google cloud platform for this project is disabled please go to https://console.cloud.google.com/apis/api/firebase.googleapis.com/overview?project=<YOUR_PROJECT> and enable"
but for some reason the UI is very un-clear
Very simple solution, go to the link below and enable your project:
https://console.cloud.google.com/apis/api/firebase.googleapis.com/overview?project=
While in my case, the issue was caused by my ad blocker. I opened network monitor through developer tools and found out that my ad blocker was canceling post requests sent by Firebase. Disabling it for Firebase solved my issue.
I was using Brave , stopped ad blocker but still it does not work , Use Chrome if nothing works ....it worked for me..
I'm hosting a web app with Firebase hosting service.
I build my app and then deploy it using firebase command tools.
The build is successful and the firebase domain shows the update:
https://calmeet-a7271.firebaseapp.com/e/-KsC5suhESWNwzYw6rtq
But the connected domain doesn't show the update:
https://calmeet.co
You can see the difference in these two links by the Settings (cog) button on the top right. https://calmeet-a7271.firebaseapp.com/e/-KsC5suhESWNwzYw6rtq has the settings button while https://calmeet.co does not
I'm not sure what I'm doing wrong, I thought this would be automatic.
DNS seem to be working alright. I don't see any error in firebase
I had this same issue. It was caused by doing back to back ng-build and firebase deploy commands in the terminal.
Turns out chrome was caching my connected site. If I opened it in a different browser (safari) it would update. Another way to fix it in chrome is to clear recent browsing data by going to your browser toolbar, clicking More and then More Tools and then Clear Browsing Data.
Short answer, Clear caching browse and try again or open another browser.
Hope this help.
Just do a hard refresh (cmd + shift + r) on your website on Chrome. That worked for me.