We're using the WebAuthenticationBroker to connect to OAuth providers such as Facebook, Flickr and Instagram in our Windows 10 UAP app. When the OS is in tablet mode, the header bar of the WebAuthenticationBroker dialog is hidden, leaving the user no way to cancel out of the dialog. Is there any way to force the header of the control to remain visible when in tablet mode? Or should the onus be on the Oauth provider to render a control on their authorization page that redirects to the callback URL provided when the broker was invoked?
UPDATE:
Microsoft has acknowledged this issue and have fixed this in the current Insider Fast Preview Build. They've added a back button to the WebAuthenticationBroker in tablet mode similar to the control on the desktop mode's interface. This will allow a user to dismiss the dialog if they choose not to authenticate or wish to cancel out of an error state.
By default, tablet mode is like the Mobile view, no title bar for dialogs (most cases).. and you can't customize the auth broker view :(
As a workaround, you can manually do it by a webview control if you really have to customize it.
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 PWA and I can run it as standalone (if user clicks icon on a device) or I can run as normal website (if user enter URL directly into web browser).
Is it possible to redirect page (open as standalone) if user open it as non standalone?
My manifest file already contain standalone parameter:
"display": "standalone"
I need something to start with.
As far as I know you need to "install" the pwa on the user device first.
By clicking the icon on the device (meaning you already installed the app there) you open the PWA that will be rendered as described in the web manifest (standalone in your case).
If you wouldn't have already installed the pwa on the device, you would have the same behaviour you are getting on your desktop by accessing the web site with the browser.
Let me know if I misunderstood your question.
UPDATE
The answer to your question (in the comment) is no (from a desktop browser). Chrome on an Android device uses/opens directly the PWA version, if installed of course. This is due to the Android Intent Filters that enable this.
But this is not the case from a desktop browser, where the user accesses the web site by entering the url manually. Maybe in the future it might change, but at the moment it is not possible.
In Chrome on desktop, if the PWA is installed and the user opens the app in the browser, there's a "To open this link, choose an app" link at top right on the address bar, between the password manager key and the bookmarks star - you could point that out to the user. Clicking that link offers a button to open the PWA and close the browser tab.
Trying to employ kiosk based on Chrome browser. Just Installed Kiosk app extension, everything is fine, but in Chrome's application mode there are no toolbar. I basically need "Back", "Forward", "Home" buttons. Is there any way to enable toolbar in app mode, or add it when extension creates window?
Navigation is not meaningful for Chrome Apps. It is, in fact, disabled.
So if your app changes state, you need custom controls for that state anyway.
If you have embedded web content in the app in a <webview>, then you need to make your own custom controls for that. See the browser app sample.
Is it possible to create a Chrome shortcut that will launch a web app in such a way that users will not be able to view or access the URL of the web app via Chrome, e.g., via the address bar, status bar, developer tools, etc. If not, would it be possible if I packaged the web app as a Chrome app? I should note that I am not concerned about the shortcut itself containing the URL, e.g., in its "Properties", because I already have an executable will which launch the shortcut. All I care about is the user not being able to view the app from within Chrome itself once the app has been launched, at least not easily.
I have tried adding Chrome flags/switches, namely, kiosk mode, fullscreen mode, and app mode, but none of them work 100% as needed. Kiosk and fullscreen modes will launch as such only if no other instances of Chrome are open; if another instance of Chrome is already open, both modes will launch in a regular view mode in which users can see the URL in the address bar. App mode (I added "--app=http://www.example.com" to the end of the "Target" property of the shortcut) is promising because it launches with no browser chrome, but I notice that if I refresh the page while in app mode, I can see the URL both in the top window bar and the bottom-left status bar. Also, app mode doesn't prevent the user from opening Developer Tools, which makes viewing the URL trivial.
Any ideas welcome!
I'm developing a mobile wep app, and would like to allow my users to login using Facebook connect.
I initially implemented the standard Oauth2 authentication, but I found a couple issues:
When I install the app as a home screen shortcut and the user needs to authenticate the user is redirected to facebook's site for authentication in normal safari. When the user is redirected back, the user is still in safari (with the top and bottom nav bars). This is obviously sub-optimal as I'd like to have the full-screen appearance
I can't get logout to work properly, there appears to be a m_user cookie left on facebook.com that is the username of the user that was previously logged in.
I thought, perhaps, that I could switch to the javascript SDK for facebook connect and render a pop-over instead of the redirect dance, but it looks like this is a pop-up only experience. When I try it on the simulator it appears the home screen shortcut is broken out of to safari, and then after login the user isn't even logged in (and the screen remains blank).
Any ideas on the smoothest way of using Facebook connect on a mobile web (HTML5) app, especially if the homescreen shortcut is to be retained?
thanks!
-simon
Have you tried the latest Javascript SDK to accomplish this? https://developers.facebook.com/docs/reference/javascript/