I have 2 applications one is asp .net application with MSAL.Net and other one is power apps application, I used iframe for silent login and it was working everywhere before chrome and firefox upgrade. After upgrading chrome and firefox browser it stop working into Incognito mode of chrome and Private mode of firefox stop working and giving below errors.
From Chrome
From Firefox
Can you please help me to resolve this issue by code instead manually do browser setting
Thanks,
Sandy
Chrome 83+ in incognito mode, has an option by default
(x) Block third-party cookies in Incognito. Disable this.
As a proper fix, use a custom domain name so that the browser no longer considers it a third party:
https://learn.microsoft.com/en-us/azure/active-directory-b2c/custom-domain?pivots=b2c-custom-policy
In private mode, please enable cookies in your browser in order for msal to work properly. This information has to be added to your cookie policy as well to make the users of your application aware.
Related
I have a Trusted Web Activity app that is displaying a Progressive Web Application by using the Android Browser Helper. The documentation and code indicates that the mobile app only runs properly when the Chrome Browser is 72 or above. The address bar is visible when the Chrome Browser is outdated. I believe I have the option of a Webview-fallback but I prefer not to use Webview as some of the app's functionality is incompatible with Webview.
While testing, when the Chrome Browser is updated on the same device, the trusted web activity runs without any issues.
What options do I have where the address bar isn't visible?
Is the min SDK the only way to set the minimum browser requirements or can I explicitly set a min Chrome Browser version in the Play Console for the app before the user downloads it? (which prompts the user to update the browser before installation)
Thanks in advance!
It's not possible to set a browser version requirement on the Play Console.
Besides falling back to a WebView, or showing the application with the URL bar, the other solution would to block the application from loading and ask the user to update / install a browser that supports Trusted Web Activity.
I have a web application which supports two click once applications. The web application works well under IE11 and both click once application launch under IE11. However I was recently trying to get my web application to operate under Chrome version 65. I installed the following ClickOnce extension under Chrome:
Meta4 ClickOnce Launcher
Now the above extension would not launch the supporting Click Once application in Chrome. The Click Once applications were developed in VS 2010.
I use php to call the Click Once application
header( 'Location: http://sanplic02.corp.mycompany.com/LaunchCatia/LaunchCatiaPWBSTART.application?licence=DP2&computername='.DisplayComputerName());
Does anybody have any ideas as to why this is so.
Any help much appreciated.
Now I eventually got my web application to work in Chrome. All of the above is correct. The extension I used was the Meta4 Click Once Launcher. The line of php code above is also correct this is how I launch the click once application supported by the web application.
So what was the underlying problem. Well essentially I was disabling my submit buttons in code. Even though the submit buttons were programmatically disabled they operated correctly under IE11 another words the submit buttons appeared enabled in IE11. However in chrome on the other hand they were disabled, hence Chrome would not execute the script that launched the click once application script. So once I removed the code to disable the submit button all went well.
The joys of cross browser compatibility.
This is not a problem with viewing the GTM console on my domain.
When I click the "preview" button my GTM interface refresh, but it just won't go into preview mode! Never had this problem before and I've tried closed and opened chrome, disabled cache in devTools and tried it in incognito. Nothing of this works.. Any ideas?
I have admin with publish rights for my account.
Solved it!
One of my Chrome extensions blocked it for some reason I don't know.
It was the extension "Ghostery" that caused the problem and when I deactivated it "preview and debug" started working.Now I just have to find out a way to still use the extension and keep GTM working, like it did before christmas.
I have found that if you are blocking third-party cookies, the GTM Preview/Debug won't turn on.
I've never got Preview mode to work in Chrome.It does work using Opera. You can get an add-on for Opera that will allow you to use all Chrome extensions in Opera.
I'm trying to load http://m.zara.com from my desktop browser. I have tried with Chrome developer tools to change the user agent to mobile. I have also installed User-Agent Switcher plugin for Chrome without any success. For some reason it is always redirecting to the desktop version.
Why is this not working? How could I manage to do this?
Checkout the link here
Try to download user-agent extension in chrome browser and then you can use the online parsers available in this blog.
There by the simulation of browsers can happen for cross browser access.
Does anybody know how to implement receiving of push notifications outside and without running browser?
There is some nuance to this:
Chrome for Android: Push messages will wake up the Service Worker and Web App even if the browser is closed. This is the default and our ideal position across all platforms
Desktop Chrome: Push works and will wake up the service worker if the browser is still open. However it will not work if the browser is closed. You can force the browser to remain open if you have a Chrome App that is set to run in the background. Other than that we (the Chrome team) are working out how we enable this by default on Windows, Mac and Linux.
Chrome for iOS: Push just does not work on this platform
Chromium blog has a post with code examples: http://updates.html5rocks.com/2015/03/push-notificatons-on-the-open-web
And the documentation was updated too: https://developer.chrome.com/apps/cloudMessaging
It is possible to write Chrome extension where background script can run if Chrome is allowed to run in the background (configurable in settings) and it can use GCM.